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?
to your account
Any service / client pair will do, e.g.:
ros2 run demo_nodes_cpp add_two_ints_server
ros2 run demo_nodes_cpp add_two_ints_client
Client sends request, servers gets request then sends response, and client gets response.
The client will hang some times and not get any result. How often that happens seems to vary on a platform and RMW implementation.
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:
Sorry, something went wrong.
@MiguelCompany @richiprosima it'd be great if a fix for rmw_fastrtps_cpp landed before Foxy gets released.
@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.
No branches or pull requests