Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

bleskes
Copy link
Contributor

@bleskes bleskes commented Nov 2, 2014

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).

… 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);
Copy link
Member

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

Copy link
Contributor Author

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

@martijnvg
Copy link
Member

@bleskes This looks good. I left two questions / comments.

@bleskes
Copy link
Contributor Author

bleskes commented Nov 3, 2014

@martijnvg thx. responded.

@martijnvg
Copy link
Member

@bleskes LGTM

@bleskes bleskes closed this in f1f50ac Nov 3, 2014
bleskes added a commit that referenced this pull request Nov 3, 2014
… 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
@bleskes bleskes deleted the min_master_nodes_validation branch November 3, 2014 13:59
@clintongormley clintongormley added the :Distributed/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure label Mar 19, 2015
@clintongormley clintongormley changed the title Discovery: don't accept a dynamic update to min_master_nodes which s larger then current master node count Don't accept a dynamic update to min_master_nodes which is larger then current master node count Jun 6, 2015
@clintongormley clintongormley added :Core/Infra/Settings Settings infrastructure and APIs and removed :Distributed/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure labels Jun 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants