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
Docs: Document the most important changes to zen discovery. #7746
Conversation
|
||
Each cluster must have an elected master node in order to be fully operational. Once a node loses its elected master | ||
node it will reject operations. |
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.
maybe add some or all? i.e., "node it will reject some or all operations".
LGTM in general, left some minor comments. Would love @clintongormley or @polyfractal to have a look as well. |
Updated the PR and applied @bleskes's feedback. |
what operations should be rejected when there is no active master. | ||
|
||
The `discovery.zen.no_master_block` setting has two valid options: | ||
* `all` - All operations on the node. I.e., both read & writes will be rejected. |
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.
Does this include read-only cluster-metadata APIs like Node Stats, Cluster State, etc? Should probably add a note regardless of what the answer is, just to be explicit.
Left a few comments. LGTM overall! :) |
Updated the PR and applied @polyfractal's feedback. |
👍 LGTM |
No description provided.