-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large number of consecutive messages queued/delayed when using RMW Fast-RTPS 6.2.2 (with Fast DDS 2.6.3) #656
Comments
@MiguelCompany @EduPonz Can you take a look? |
@nvcyc do we have the same problem with rolling? |
We have not tried on Rolling. Is there a version of the fastrtps-rmw this may already be resolved in and would it be compatible with Humble? |
Just thought there could be difference, if it does not happen in rolling, that would be also information track the problem.
just curious, why you guys use these specific branches?
that means you use Foxy as Tier I, right? Why not using foxy branch for
This is incorrect.
|
I guess the OP is referring to rmw_fastrtps 6.2.2; the corresponding Fast DDS version should be v2.6.2. Is that correct @nvcyc? In that case, it'd be great if you could update the ticket description |
Thanks for helping me clarify the versions in discussion. Yes, I was initially referring to the RMW FastRTPS I just tested Fast DDS 2.6.4 that contains the PR @Mario-DL mentioned with RMW FastRTPS I'll rebuild our environment with |
I'm going to assume that this was fixed by 2.6.4, and close this out. If that is not the case, please feel free to reopen. |
Bug report
Required Info:
rosinstall_generator
6.2.1
: https://github.com/ros2/rmw_fastrtps/tree/6.2.16.2.2
: https://github.com/ros2/rmw_fastrtps/tree/6.2.26.2.2
2.6.3
Steps to reproduce issue
With the
RMW Fast-RTPS 6.2.2
(which is the version currently associated with Humble when installed using rosinstall_generator), when continuously publishing messages from a publisher to a subscriber, we observed that intermittently a large number of consecutive messages may be queued and not delivered to the subscriber immediately for unknown reasons at random timesWhen such a symptom happened, we also observed that some of those queued messages can be successfully delivered to the subscriber (i.e., the subscriber’s callback is called) after stopping publishing messages and starting to publish new messages.
This symptom seems to happen more often when the message publisher rate is high, yet it can still be observed occasionally when the rate is low.
This issue is not observed once we downgrade
RMW Fast-RTPS to 6.2.1
.Expected behavior
With
RMW Fast-RTPS 6.2.1
, messages are delivered as expected.Actual behavior
With
RMW Fast-RTPS 6.2.2
, a large number of consecutive messages may be queued and not delivered to their subscriber at random times.The text was updated successfully, but these errors were encountered: