# Index relocation during initialization **URL:** \ **Category:** Elasticsearch\ **Created:** [September 12, 2013, 8:59am UTC](https://discuss.elastic.co/t/index-relocation-during-initialization/13567 "2013-09-12T08:59:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [September 12, 2013, 8:59am UTC](https://discuss.elastic.co/t/index-relocation-during-initialization/13567/1 "2013-09-12T08:59:11Z")
Hi there, Whenever we restart a node (or a few) in a cluster, and also when we do a full cluster restart, the cluster takes a lot of time to recover from YELLOW state to GREEN. What we observed is the cluster is relocating indexes when it goes up, or when a few nodes restarted. Since our indexes are not small it takes them time to relocate, and also one relocation triggers another (for balancing reasons) this becomes a never ending pursuit. As long as the cluster is up - no relocations happen. This only happens when a node or few restart, or when the cluster restarts as a whole. But still - a balance that is preserved while the cluster is up should be preserved when there's a small disturbance. I will only expect a rebalance when a game-changer event happens - large index is added or removed, or a node permanently joins / removed. I'm aware of the various settings in place that should prevent that (expected number of nodes, time to wait etc) but obviously they don't play well. Our hope is the new allocation decider would help with that, but that issue seems to be originating from some sort of a bug in the decision of WHEN to try rebalancing. I'll be happy to provide anything that could help pinpoint the issue Itamar. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [September 12, 2013, 12:32pm UTC](https://discuss.elastic.co/t/index-relocation-during-initialization/13567/2 "2013-09-12T12:32:12Z")
Hi Itamar > I'm aware of the various settings in place that should prevent that > (expected number of nodes, time to wait etc) but obviously they don't play > well. Why do you say the don't play well? You don't mention what those settings are in your cluster, and they're not settings that we can determine automatically because we don't know how many nodes you expect to have in your cluster. Those settings are designed specifically to prevent the situation you describe and in my experience, they work very well. So I'm guessing that you don't have them configured correctly clint -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [September 12, 2013, 12:38pm UTC](https://discuss.elastic.co/t/index-relocation-during-initialization/13567/3 "2013-09-12T12:38:25Z")
Because we've set them correctly, and still seeing this behavior. It might be something unique to our scenario (rolling indexes, each is quite big). I will triple-triple-check and get back to you. I wish there was an easy way to reproduce this in a test. On Thu, Sep 12, 2013 at 2:32 PM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)wrote: > Hi Itamar > > > I'm aware of the various settings in place that should prevent that > > (expected number of nodes, time to wait etc) but obviously they don't play > > well. > > Why do you say the don't play well? You don't mention what those settings > are in your cluster, and they're not settings that we can determine > automatically because we don't know how many nodes you expect to have in > your cluster. Those settings are designed specifically to prevent the > situation you describe and in my experience, they work very well. So I'm > guessing that you don't have them configured correctly > > clint > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![ananth](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@ananth](https://discuss.elastic.co/u/ananth)\ **Post date:** [February 5, 2014, 7:15am UTC](https://discuss.elastic.co/t/index-relocation-during-initialization/13567/4 "2014-02-05T07:15:10Z")
Hi Clinton, We are also facing the issue , I verified recovery starts only after expected nodes arrived. In case of full cluster restart , initially all the shards become unavailable and master starts allocate unassigned nodes. While allocation BalancedShardAllocator comes to play which change the previously balanced allocation(before full restart). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cd4a5c5e-660d-4c67-b01d-0064ee6ea1c5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cd4a5c5e-660d-4c67-b01d-0064ee6ea1c5%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:52am UTC](https://discuss.elastic.co/t/index-relocation-during-initialization/13567/5 "2017-07-06T01:52:31Z")