database: Increase the default "promote" timeout (bsc#1131791)#2124
Closed
toabctl wants to merge 1 commit into
Closed
database: Increase the default "promote" timeout (bsc#1131791)#2124toabctl wants to merge 1 commit into
toabctl wants to merge 1 commit into
Conversation
When a galera cluster is out of sync and needs a resync, the cluster may decide to wipe the available data on the out-of-sync nodes and do a full resync to *all* (except the bootstrap node of course) cluster nodes. In a 3-node cluster, it means that the data needs to be transfered 2x. To not run into timeouts in that case, increase the timeout to 10 minutes.
Contributor
Author
|
Already a PR available: #2114 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When a galera cluster is out of sync and needs a resync, the cluster
may decide to wipe the available data on the out-of-sync nodes and do
a full resync to all (except the bootstrap node of course) cluster
nodes. In a 3-node cluster, it means that the data needs to be
transfered 2x.
To not run into timeouts in that case, increase the timeout to 10
minutes.