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

No need to reroute (check for possible shard allocations) when a new *non* data node is added to the cluster #1368

Closed
kimchy opened this issue Sep 27, 2011 · 0 comments

Comments

@kimchy
Copy link
Member

commented Sep 27, 2011

No description provided.

@kimchy kimchy closed this in 4088236 Sep 27, 2011

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.