-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix configure-hash-rings.md there is a switch of value for cluster-label-verification-disabled #9486
Conversation
…l-verification-disabled > 5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=true`. Need to be false if we want to enable cluster-label-verification-disabled : > 5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=false`.
@@ -108,7 +108,7 @@ Any traffic that does not match that prefix is discarded, to ensure that only th | |||
This label must be the same on all instances that are part of the same cluster. | |||
For example, if you run a Grafana Mimir cluster in a dedicated namespace, then set the cluster label to the name of the namespace. | |||
4. **Wait** until the configuration change has been rolled out to all Grafana Mimir instances. | |||
5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=true`. | |||
5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=false`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This step ENABLES cluster label verification by REMOVING existing -memberlist.cluster-label-verification-disabled=true
option. (After removal, default value will be used, which is false
).
(That is, suggested edit is currently wrong).
@@ -108,7 +108,7 @@ Any traffic that does not match that prefix is discarded, to ensure that only th | |||
This label must be the same on all instances that are part of the same cluster. | |||
For example, if you run a Grafana Mimir cluster in a dedicated namespace, then set the cluster label to the name of the namespace. | |||
4. **Wait** until the configuration change has been rolled out to all Grafana Mimir instances. | |||
5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=true`. | |||
5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=false`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=false`. | |
5. Enable cluster label verification on all cluster instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=false`. |
Need to be false if we want to enable cluster-label-verification :
What this PR does
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.