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

Only allow rebalance operations to run if all shard store data is available #14652

Merged
merged 1 commit into from
Nov 11, 2015

Conversation

s1monw
Copy link
Contributor

@s1monw s1monw commented Nov 10, 2015

This commit prevents running rebalance operations if the store allocator is
still fetching async shard / store data to prevent pre-mature rebalance decisions
which need to be reverted once shard store data is available. This is typically happening
on rolling restarts which can make those restarts extremely painful.

Closes #14387

this is the 1.7 backport of #14591

…ilable

This commit prevents running rebalance operations if the store allocator is
still fetching async shard / store data to prevent pre-mature rebalance decisions
which need to be reverted once shard store data is available. This is typically happening
on rolling restarts which can make those restarts extremely painful.

Closes elastic#14387
@s1monw s1monw added the review label Nov 10, 2015
@s1monw
Copy link
Contributor Author

s1monw commented Nov 10, 2015

@bleskes can you take a quick look - it's the 1.7 backport

@@ -1251,7 +1251,7 @@ public void restartRandomNode(RestartCallback callback) throws Exception {
* Restarts a random data node in the cluster
*/
public void restartRandomDataNode() throws Exception {
restartRandomNode(EMPTY_CALLBACK);
restartRandomDataNode(EMPTY_CALLBACK);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:)

@bleskes
Copy link
Contributor

bleskes commented Nov 10, 2015

LGTM

s1monw added a commit that referenced this pull request Nov 11, 2015
Only allow rebalance operations to run if all shard store data is available
@s1monw s1monw merged commit 15ba56a into elastic:1.7 Nov 11, 2015
@s1monw s1monw deleted the 17_backport_pull/14591 branch November 11, 2015 13:05
@lcawl lcawl added :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. and removed :Allocation labels Feb 13, 2018
@clintongormley clintongormley added :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) and removed :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. labels Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) v1.7.4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants