Restore shunned server (due to replication lag) state on commit, provided that the replication lag is below the maximum threshold. #4450
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
…ly upon commit (triggered by the command LOAD MYSQL SERVERS TO RUNTIME), provided that the replication lag is below the maximum threshold.
rahim-kanji
changed the title
Renamed variable from: mysql-recover_replication_lag_shunned_servers_on_comit to: mysql-evaluate_replication_lag_on_servers_load
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.
Introduced a new variable named
mysql-recover_replication_lag_shunned_servers_on_committo restore servers that are in shunned state due to replication lag on commit (triggered by the command LOAD MYSQL SERVERS TO RUNTIME), provided that the replication lag is below the maximum threshold.Note:
Default value of
mysql-recover_replication_lag_shunned_servers_on_commitistrue