WAL replay hangs if the response wasn't received #535
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
lgtm |
pauldix
added a commit
that referenced
this pull request
May 13, 2014
WAL replay hangs if the response wasn't received
jvshahid
added a commit
that referenced
this pull request
May 27, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The way the WAL works is by sequentially and synchronously sending write requests to other nodes using
ClusterServer.MakeRequest.MakeRequestis inherently problematic, since it will block indefinitely waiting for the response, if the response wasn't receivedMakeRequestwill never return. In the case of the WAL, that means replication will stop completely until the server is bounced.