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
Flaky services performance #922
Comments
CC @jacobperron |
@MiguelCompany @richiprosima it'd be great if a fix for |
@hidmic I've just created ros2/rmw_fastrtps#390, which should fix the issue of sending a response when the reader has not yet been matched. |
Closing in favor of ros2/rmw_fastrtps#392 and ros2/rmw_cyclonedds#191 since these appear to be duplicates and the other two are on more specific repos. |
hidmic commentedMay 20, 2020
•
edited
Bug report
Required Info:
rclcpp
Steps to reproduce issue
Any service / client pair will do, e.g.:
and
Expected behavior
Client sends request, servers gets request then sends response, and client gets response.
Actual behavior
The client will hang some times and not get any result. How often that happens seems to vary on a platform and RMW implementation.
Additional information
Issues with services performance has been observed before, as early as ros2/demos#304. More recent occurrences may be found in ros2/rmw_cyclonedds#185, ros2/system_tests#420 and ros2/rmw_cyclonedds#74. Nondeterministic as it is, it has seemed resolved in the past, suggesting race conditions as root cause.
Parameter servers as well as action servers and clients relying on services for their implementation are also likely to be negatively affected by this issue.
The text was updated successfully, but these errors were encountered: