keeper: report error when local dbuid is not correct #510
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
keeper_report_error_when_local_dbuid_is_not_correct
branch
from
107e1bb
to
9b40264
Compare
if the local dbuid is different than the clusterdata required one but initmode is none something bad happened to the local keeper data. This should happen only when the local dbstate file disappeared (ephemeral data dir, manual remove). In such case don't just update it with the clusterdata one and continue but report an error and stop.
sgotti
force-pushed
the
keeper_report_error_when_local_dbuid_is_not_correct
branch
from
9b40264
to
2c818a0
Compare
sgotti
added a commit
that referenced
this pull request
Jun 15, 2018
…uid_is_not_correct keeper: report error when local dbuid is not correct
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.
if the local dbuid is different than the clusterdata required one but initmode
is none something bad happened to the local keeper data. This should happen only
when the local dbstate file disappeared (ephemeral data dir, manual remove). In
such case don't just update it with the clusterdata one and continue but report an
error and stop.