-
Notifications
You must be signed in to change notification settings - Fork 793
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
Fix deadlock with LivelinessManager [11925] #2037
Conversation
Signed-off-by: Ricardo González Moreno <ricardo@richiware.dev> Signed-off-by: Ricardo González Moreno <ricardo@richiware.dev>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe unrelated to this PR, but should we add liveliness assertion on StatelessReader::processHeartbeatMsg
?
Signed-off-by: Ricardo González Moreno <ricardo@richiware.dev>
Reliable Datawriters will never send a heartbeat to Besteffort Datareaders. Only in case of using multicast but I think a Besteffort Datareader will never expect a heartbeat, then it will never do something if received one. |
I am thinking of the case when the liveliness is set to |
After discussing this offline, we will do this in a separate PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Ricardo González Moreno <ricardo@richiware.dev> Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Fixes a deadlock when asserting liveliness of a writer (due to a sample was received from it).