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

Optimize multiple cluster state processing on receiving nodes #5139

Closed
kimchy opened this issue Feb 17, 2014 · 0 comments
Closed

Optimize multiple cluster state processing on receiving nodes #5139

kimchy opened this issue Feb 17, 2014 · 0 comments
Labels
:Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. >enhancement v0.90.12 v1.0.1 v1.1.0 v2.0.0-beta1

Comments

@kimchy
Copy link
Member

kimchy commented Feb 17, 2014

Nodes that receive the cluster state, and they have several of those pending, can optimize and try and process potentially only one of those.

@kimchy kimchy closed this as completed in 8601529 Feb 17, 2014
kimchy added a commit that referenced this issue Feb 17, 2014
Nodes that receive the cluster state, and they have several of those pending, can optimize and try and process potentially only one of those.
closes #5139
kimchy added a commit that referenced this issue Feb 17, 2014
Nodes that receive the cluster state, and they have several of those pending, can optimize and try and process potentially only one of those.
closes #5139
kimchy added a commit that referenced this issue Feb 17, 2014
Nodes that receive the cluster state, and they have several of those pending, can optimize and try and process potentially only one of those.
closes #5139
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
Nodes that receive the cluster state, and they have several of those pending, can optimize and try and process potentially only one of those.
closes elastic#5139
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
Nodes that receive the cluster state, and they have several of those pending, can optimize and try and process potentially only one of those.
closes elastic#5139
@clintongormley clintongormley added :Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. and removed :Cluster labels Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. >enhancement v0.90.12 v1.0.1 v1.1.0 v2.0.0-beta1
Projects
None yet
Development

No branches or pull requests

2 participants