-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Federated execution without deadlines fail in actually distributed environments #2034
Comments
How exactly does it fail? (The test is hard to replicate). |
I'll leave the logs. The debug messages are too much, so I kind of cut off the middle part. Sorry for the readability. RTI DEBUG logs.
federate0.log
fed1.log
|
A quick observation from me is that the system clock on the RPis are terribly out of sync. They start in 1969. In theory, our distributed infrastructure should be able to handle this, but I wouldnt be surprised if there are some edge-cases arising when we try to adjust the clocks by 50 years. This definitely deserves debugging, but an easy workaround for you would be disabling clock-sync and use NTP or PTP instead. If the RPis have internet access they can just run a simple NTP client. If they dont have internet access you could look into running linuxPTP and phc2sys on your Ubuntu and the RPis. This would rely on software timestamping but should work fine. |
@Jakio815 Can you try out this bug-fix: lf-lang/reactor-c#288 |
I'll take a look, but not sure what's really the problem. Is it even related with #2048 ? |
What I mean is that I believe this PR will fix your issue. I also experienced wierd behaviors on RPi and found this overflow bug |
The fix is merged into the main branch of |
The federated execution works well on local machines, running all processes on one machine.
However, if there are no deadlines, it fails in actually distributed environments.
I've made an experiment running
SimpleFederated.lf
on a Ubuntu RTI server, and two Raspberry Pis.The
SimpleFederated.lf
looks like this, and is intest/C/src/federated/SimpleFederatedAuthenticated.lf
It does not have any deadlines, but only timeouts, and fails.
The text was updated successfully, but these errors were encountered: