Clarify message emitted on cluster UUID mismatch (#66915) #66926
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
DaveCTurner
added
>enhancement
:Distributed Coordination/Cluster Coordination
elasticmachine
added
the
Team:Distributed
|
Pinging @elastic/es-distributed (Team:Distributed) |
Today we report a join failure due to a cluster UUID mismatch with the
following (accurate, but mystifying) message:
join validation on cluster state with a different cluster uuid [...] than local cluster uuid [...], rejecting
This tends to occur mostly when setting up a cluster for the first time
and gives users no clue what they've actually done wrong or what they
should do to fix it.
This commit adjusts this message to indicate that the problem is likely
discovery or cluster bootstrapping configuration and indicates that the
cluster UUID persists across restarts and suggests the usual fix of
wiping the node's data path to get out of the mess.
Backport of elastic#66915 to 7.x.
DaveCTurner
force-pushed
the
2021-01-04-cluster-uuid-mismatch-message-7x
branch
from
ee21aa8
to
94355da
Compare
|
Failure is #66278 |
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.
Today we report a join failure due to a cluster UUID mismatch with the
following (accurate, but mystifying) message:
This tends to occur mostly when setting up a cluster for the first time
and gives users no clue what they've actually done wrong or what they
should do to fix it.
This commit adjusts this message to indicate that the problem is likely
discovery or cluster bootstrapping configuration and indicates that the
cluster UUID persists across restarts and suggests the usual fix of
wiping the node's data path to get out of the mess.