Override master promotion: apply post-unsuccessful processes #947
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
shlomi-noach
temporarily deployed
to
production/mysql_cluster=conductor
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.
Refactoring the code and consequences of overriding a master promotion.
Overriding a promotion happens if:
FailMasterPromotionIfSQLThreadNotUpToDateis metDelayMasterPromotionIfSQLThreadNotUpToDateis unsuccesfulPreviously, these overrides would report as if promotion was not attempted.
From now on, the failover will be reported as attempted and failed.
The consequence is that
PostUnsuccessfulFailoverProcesseswill be executed if master override took place. This is the logic we would expect: the promotion failed due to whatever constraint.