sentinel: don't choose keepers with db behind a defined lag as masters. #268
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
sgotti
force-pushed
the
handle_max_standby_lag
branch
from
109833a
to
3e29e5f
Compare
Add a new cluster spec option `MaxStandbyLag` which defaults to 1MiB and honor its value when choosing eligible standbys/old master. Fixes sorintlab#251
sgotti
force-pushed
the
handle_max_standby_lag
branch
from
3e29e5f
to
5587b86
Compare
sgotti
added a commit
that referenced
this pull request
Apr 25, 2017
sentinel: don't choose keepers with db behind a defined lag as masters.
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.
Add a new cluster spec option
MaxStandbyLagwhich defaults to 1MiB andhonor its value when choosing eligible standbys/old master.
Fixes #251