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
Don't accept a dynamic update to min_master_nodes
which is larger then current master node count
#8321
Conversation
… larger then current master node count The discovery.zen.minimum_master_nodes setting can be updated dynamically. Settings it to a value higher then the current number of master nodes will cause the current master to step down. This is dangerous because if done by mistake (typo) there is no way to restore the settings (this requires an active master).
|
||
@Test | ||
public void testCanNotBringClusterDown() throws ExecutionException, InterruptedException { | ||
int nodeCount = scaledRandomIntBetween(1, 1); |
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 the max should be more? Something like 5
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.
I had commit on my machine I forget to push changing this back to it's original value - 10
@bleskes This looks good. I left two questions / comments. |
ad4ed9c
to
31c2f55
Compare
@martijnvg thx. responded. |
@bleskes LGTM |
… larger then current master node count The discovery.zen.minimum_master_nodes setting can be updated dynamically. Settings it to a value higher then the current number of master nodes will cause the current master to step down. This is dangerous because if done by mistake (typo) there is no way to restore the settings (this requires an active master). Closes #8321
min_master_nodes
which is larger then current master node count
The discovery.zen.minimum_master_nodes setting can be updated dynamically. Settings it to a value higher then the current number of master nodes will cause the current master to step down. This is dangerous because if done by mistake (typo) there is no way to restore the settings (this requires an active master).