Skip to content
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

GEODE-7055: Don't send failure replies from a P2P reader thread #3894

Conversation

upthewaterspout
Copy link
Contributor

We were hitting a deadlock during startup if a P2P reader thread tried
to send a failure reply - it would block waiting for startup to finish,
but startup would not finish until the P2P reader thread could read a
startup response.

Send the failure reply in a separate thread, to make sure we always
unblock the P2P reader thread to read new messages.

We were hitting a deadlock during startup if a P2P reader thread tried
to send a failure reply - it would block waiting for startup to finish,
but startup would not finish until the P2P reader thread could read a
startup response.

Send the failure reply in a separate thread, to make sure we always
unblock the P2P reader thread to read new messages.
Copy link
Contributor

@bschuchardt bschuchardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I talked with Dan about the need to use an executor to send the reply & agree with this change.

@upthewaterspout upthewaterspout merged commit 1438b56 into apache:develop Aug 8, 2019
@upthewaterspout upthewaterspout deleted the feature/deadlock-on-failure-reply-GEODE-7055 branch August 8, 2019 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants