PXC434 PXC-436 Crash in galera at certification #34
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
peterschwaller
changed the title
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.
In some rare scenarios (e.g., when we have multiple transactions awaiting certification, and the last node remaining in the cluster becomes PRIMARY due to the failure of the previous primary node and the assign_initial_position() was called) sequence number mismatch occurs on configuration change and then certification was failed. In some other rare scenarios, states diverged on SST and we see the local state sequence number is greater than group sequence number. In both cases we cannot move server forward to avoid potential data loss, and hence will have to shut it down. This patch eliminates the server crash because of the assert(0) or falling into exception handler (in the above scenarios).