# Just initialize shards when problems but no rebalance **URL:** \ **Category:** Elasticsearch\ **Created:** [January 14, 2015, 9:57pm UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651 "2015-01-14T21:57:06Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Matias\_Waisgold](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@Matias\_Waisgold](https://discuss.elastic.co/u/Matias_Waisgold)\ **Post date:** [January 14, 2015, 9:57pm UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/1 "2015-01-14T21:57:06Z")
Hi is there any setting that I can put to ES that it automatically assigns shards that are unassigned but never ever rebalance the cluster? I´ve found several issues when rebalancing and prefer to do it manually. If I set cluster.routing.allocation.enable to "none" nothing happens. If I set it to "all" then it starts rebalancing. Is it ok to combine cluster.routing.allocation.allow\_rebalance to "none" and cluster.routing.allocation.enable to "all". The issue is mainly because we are running low on disk and when that happens elasticsearch removes all shards from an instance, that doesn´t care about cluster.routing.allocation.cluster\_concurrent\_rebalance and starts moving shards like crazy around the entire cluster, filling the storage on other instances in the way that it will never stop balancing. Kind regards -- 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/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 15, 2015, 3:09am UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/2 "2015-01-15T03:09:49Z")
You could do this, but it's a lot of manual overhead to have to deal with. However ES does have some disk space awareness during allocation, take a look at > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. On 15 January 2015 at 10:57, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) wrote: > Hi is there any setting that I can put to ES that it automatically assigns > shards that are unassigned but never ever rebalance the cluster? > I´ve found several issues when rebalancing and prefer to do it manually. > If I set cluster.routing.allocation.enable to "none" nothing happens. > If I set it to "all" then it starts rebalancing. > > Is it ok to combine cluster.routing.allocation.allow\_rebalance to "none" > and cluster.routing.allocation.enable to "all". > > The issue is mainly because we are running low on disk and when that > happens elasticsearch removes all shards from an instance, that doesn´t > care about cluster.routing.allocation.cluster\_concurrent\_rebalance and > starts moving shards like crazy around the entire cluster, filling the > storage on other instances in the way that it will never stop balancing. > > Kind regards > > -- > 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/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Matias\_Waisgold](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@Matias\_Waisgold](https://discuss.elastic.co/u/Matias_Waisgold)\ **Post date:** [January 15, 2015, 1:14pm UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/3 "2015-01-15T13:14:40Z")
Yes, I've seen that but the problem is that when the threshold is reached it removes all shards from the server instead of just removing 1 and balance. And when that happens the cluster starts to move shards over everywhere and it never stops. Another problem we are having is that in the file storage we see data from shards that are not assigned to itself so it can´t allocate anything in this dirty state. 2015-01-15 0:09 GMT-03:00 Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com): > You could do this, but it's a lot of manual overhead to have to deal with. > However ES does have some disk space awareness during allocation, take a > look at > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/index-modules-allocation.html#disk) > > On 15 January 2015 at 10:57, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) wrote: > > > Hi is there any setting that I can put to ES that it automatically > > assigns shards that are unassigned but never ever rebalance the cluster? > > I´ve found several issues when rebalancing and prefer to do it manually. > > If I set cluster.routing.allocation.enable to "none" nothing happens. > > If I set it to "all" then it starts rebalancing. > > > > Is it ok to combine cluster.routing.allocation.allow\_rebalance to "none" > > and cluster.routing.allocation.enable to "all". > > > > The issue is mainly because we are running low on disk and when that > > happens elasticsearch removes all shards from an instance, that doesn´t > > care about cluster.routing.allocation.cluster\_concurrent\_rebalance and > > starts moving shards like crazy around the entire cluster, filling the > > storage on other instances in the way that it will never stop balancing. > > > > Kind regards > > > > -- > > 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/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe). > To unsubscribe from this group and all its topics, 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/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Kimbro\_Staken](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@Kimbro\_Staken](https://discuss.elastic.co/u/Kimbro_Staken)\ **Post date:** [January 15, 2015, 4:26pm UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/4 "2015-01-15T16:26:29Z")
I've experienced what you're describing. I called it a "shard relocation storm" and it's really tough to get under control. I opened a ticket on the issue and a fix was supposedly included in 1.4.2. What version are you running? If you want to truly manually manage this situation you could set cluster.routing.allocation.disk.threshold\_enabled to false but that will likely cause other issues. I ended up just setting cluster.routing.allocation.disk.watermark.high to a really low value and actively managed shard allocations to prevent nodes from getting anywhere near that value. This is tricky as the way ES allocates shards it can easily run nodes out of disk if you're regularly creating new indices and those grow rapidly. Kimbro On Thu, Jan 15, 2015 at 6:14 AM, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) wrote: > Yes, I've seen that but the problem is that when the threshold is reached > it removes all shards from the server instead of just removing 1 and > balance. And when that happens the cluster starts to move shards over > everywhere and it never stops. > > Another problem we are having is that in the file storage we see data from > shards that are not assigned to itself so it can´t allocate anything in > this dirty state. > > 2015-01-15 0:09 GMT-03:00 Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com): > > > You could do this, but it's a lot of manual overhead to have to deal with. > > However ES does have some disk space awareness during allocation, take a > > look at > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/index-modules-allocation.html#disk) > > > > On 15 January 2015 at 10:57, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) wrote: > > > > > Hi is there any setting that I can put to ES that it automatically > > > assigns shards that are unassigned but never ever rebalance the cluster? > > > I´ve found several issues when rebalancing and prefer to do it manually. > > > If I set cluster.routing.allocation.enable to "none" nothing happens. > > > If I set it to "all" then it starts rebalancing. > > > > > > Is it ok to combine cluster.routing.allocation.allow\_rebalance to "none" > > > and cluster.routing.allocation.enable to "all". > > > > > > The issue is mainly because we are running low on disk and when that > > > happens elasticsearch removes all shards from an instance, that doesn´t > > > care about cluster.routing.allocation.cluster\_concurrent\_rebalance and > > > starts moving shards like crazy around the entire cluster, filling the > > > storage on other instances in the way that it will never stop balancing. > > > > > > Kind regards > > > > > > -- > > > 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/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe). > > To unsubscribe from this group and all its topics, 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/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Matias\_Waisgold](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@Matias\_Waisgold](https://discuss.elastic.co/u/Matias_Waisgold)\ **Post date:** [January 15, 2015, 5:55pm UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/5 "2015-01-15T17:55:53Z")
Great, thank you. We are creating another cluster with more disk space to avoid this situations. By any chance do you have the link to the issue? 2015-01-15 13:26 GMT-03:00 Kimbro Staken [kstaken@kstaken.com](mailto:kstaken@kstaken.com): > I've experienced what you're describing. I called it a "shard relocation > storm" and it's really tough to get under control. I opened a ticket on the > issue and a fix was supposedly included in 1.4.2. What version are you > running? > > If you want to truly manually manage this situation you could set > cluster.routing.allocation.disk.threshold\_enabled to false but that will > likely cause other issues. I ended up just setting > cluster.routing.allocation.disk.watermark.high to a really low value and > actively managed shard allocations to prevent nodes from getting anywhere > near that value. This is tricky as the way ES allocates shards it can > easily run nodes out of disk if you're regularly creating new indices and > those grow rapidly. > > Kimbro > > On Thu, Jan 15, 2015 at 6:14 AM, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) > wrote: > > > Yes, I've seen that but the problem is that when the threshold is reached > > it removes all shards from the server instead of just removing 1 and > > balance. And when that happens the cluster starts to move shards over > > everywhere and it never stops. > > > > Another problem we are having is that in the file storage we see data > > from shards that are not assigned to itself so it can´t allocate anything > > in this dirty state. > > > > 2015-01-15 0:09 GMT-03:00 Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com): > > > > > You could do this, but it's a lot of manual overhead to have to deal > > > with. > > > However ES does have some disk space awareness during allocation, take a > > > look at > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/index-modules-allocation.html#disk) > > > > > > On 15 January 2015 at 10:57, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) > > > wrote: > > > > > > > Hi is there any setting that I can put to ES that it automatically > > > > assigns shards that are unassigned but never ever rebalance the cluster? > > > > I´ve found several issues when rebalancing and prefer to do it manually. > > > > If I set cluster.routing.allocation.enable to "none" nothing happens. > > > > If I set it to "all" then it starts rebalancing. > > > > > > > > Is it ok to combine cluster.routing.allocation.allow\_rebalance to > > > > "none" and cluster.routing.allocation.enable to "all". > > > > > > > > The issue is mainly because we are running low on disk and when that > > > > happens elasticsearch removes all shards from an instance, that doesn´t > > > > care about cluster.routing.allocation.cluster\_concurrent\_rebalance and > > > > starts moving shards like crazy around the entire cluster, filling the > > > > storage on other instances in the way that it will never stop balancing. > > > > > > > > Kind regards > > > > > > > > -- > > > > 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/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe). > > > To unsubscribe from this group and all its topics, 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/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com) > > > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe). > To unsubscribe from this group and all its topics, 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/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAMaTqYq%2B\_S1\_CaPJ-\_HN8F%3DizX9VjKmF\_W5dhDFpAmS6kxw0WA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYq%2B_S1_CaPJ-_HN8F%3DizX9VjKmF_W5dhDFpAmS6kxw0WA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Kimbro\_Staken](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@Kimbro\_Staken](https://discuss.elastic.co/u/Kimbro_Staken)\ **Post date:** [January 15, 2015, 7:09pm UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/6 "2015-01-15T19:09:13Z")
So is this still happening with 1.4.2? Here's the ticket. Looks like the fix was supposed to be in 1.4.1 > > > I have a relatively large cluster running ES 1.3.5 and we recently started to ge…t low on disk space. The cluster has roughly 110 TB usable space of which about 86TB is used. We have 93 indices of which 90 are rotating daily indices and the other 3 are permanent. With this setup we end up with shards that range in size from a few MB to over 160GB and we're finding the shard count based allocation strategy results in some nodes starting to run out of space earlier than expected which trips the cluster.routing.allocation.disk.watermark.high setting. > > It appears when this happens that "all" of the shards from that node are relocated. This then puts more pressure on the other nodes and at some point another node will trip cluster.routing.allocation.disk.watermark.high and relocate all of its shards too. This then goes on and on and on and never stops until we intercede and manually cancel the allocations. At times we've seen more than 200 relocations in progress at the same time. > > Is the relocation of "all" shards really the intended behavior? In looking at the source code it appears to do a reroute in this scenario but this seems like the last thing you would want to do. You're almost guaranteed that if one node is tripping that setting then others are going to be close as well. In our cluster we have room on many of the other nodes and if it selectively moved a shard or two everything would be fine but moving all of them is really problematic. > > It also seems that when all these relocations occur that cluster.routing.allocation.disk.watermark.low doesn't prevent the overallocation of other nodes. I believe this is occurring because of the number of relocations that are started at once so the node gets asked multiple times to accept shards within a short time period and all requests succeed because no pending relocations are considered in respect to disk utilization. This pretty much guarantees that node will eventually trip cluster.routing.allocation.disk.watermark.high and continue the cycle even though there are other nodes in the cluster with hundreds of GB free. > > We're in the process of adding additional capacity to our cluster so we're not at risk of bumping into these limits but otherwise this behavior seems quite problematic. On Thu, Jan 15, 2015 at 10:55 AM, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) wrote: > Great, thank you. We are creating another cluster with more disk space to > avoid this situations. > By any chance do you have the link to the issue? > > 2015-01-15 13:26 GMT-03:00 Kimbro Staken [kstaken@kstaken.com](mailto:kstaken@kstaken.com): > > > I've experienced what you're describing. I called it a "shard relocation > > storm" and it's really tough to get under control. I opened a ticket on the > > issue and a fix was supposedly included in 1.4.2. What version are you > > running? > > > > If you want to truly manually manage this situation you could set > > cluster.routing.allocation.disk.threshold\_enabled to false but that will > > likely cause other issues. I ended up just setting > > cluster.routing.allocation.disk.watermark.high to a really low value and > > actively managed shard allocations to prevent nodes from getting anywhere > > near that value. This is tricky as the way ES allocates shards it can > > easily run nodes out of disk if you're regularly creating new indices and > > those grow rapidly. > > > > Kimbro > > > > On Thu, Jan 15, 2015 at 6:14 AM, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) > > wrote: > > > > > Yes, I've seen that but the problem is that when the threshold is > > > reached it removes all shards from the server instead of just removing 1 > > > and balance. And when that happens the cluster starts to move shards over > > > everywhere and it never stops. > > > > > > Another problem we are having is that in the file storage we see data > > > from shards that are not assigned to itself so it can´t allocate anything > > > in this dirty state. > > > > > > 2015-01-15 0:09 GMT-03:00 Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com): > > > > > > > You could do this, but it's a lot of manual overhead to have to deal > > > > with. > > > > However ES does have some disk space awareness during allocation, take > > > > a look at > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/index-modules-allocation.html#disk) > > > > > > > > On 15 January 2015 at 10:57, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) > > > > wrote: > > > > > > > > > Hi is there any setting that I can put to ES that it automatically > > > > > assigns shards that are unassigned but never ever rebalance the cluster? > > > > > I´ve found several issues when rebalancing and prefer to do it > > > > > manually. > > > > > If I set cluster.routing.allocation.enable to "none" nothing happens. > > > > > If I set it to "all" then it starts rebalancing. > > > > > > > > > > Is it ok to combine cluster.routing.allocation.allow\_rebalance to > > > > > "none" and cluster.routing.allocation.enable to "all". > > > > > > > > > > The issue is mainly because we are running low on disk and when that > > > > > happens elasticsearch removes all shards from an instance, that doesn´t > > > > > care about cluster.routing.allocation.cluster\_concurrent\_rebalance and > > > > > starts moving shards like crazy around the entire cluster, filling the > > > > > storage on other instances in the way that it will never stop balancing. > > > > > > > > > > Kind regards > > > > > > > > > > -- > > > > > 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/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > You received this message because you are subscribed to a topic in the > > > > Google Groups "elasticsearch" group. > > > > To unsubscribe from this topic, visit > > > > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe) > > > > . > > > > To unsubscribe from this group and all its topics, 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/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > > . > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > 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/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com) > > > [https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe). > > To unsubscribe from this group and all its topics, 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/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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/CAMaTqYq%2B\_S1\_CaPJ-\_HN8F%3DizX9VjKmF\_W5dhDFpAmS6kxw0WA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYq%2B_S1_CaPJ-_HN8F%3DizX9VjKmF_W5dhDFpAmS6kxw0WA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAMaTqYq%2B\_S1\_CaPJ-\_HN8F%3DizX9VjKmF\_W5dhDFpAmS6kxw0WA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYq%2B_S1_CaPJ-_HN8F%3DizX9VjKmF_W5dhDFpAmS6kxw0WA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAA0DmXar33evahvzhzbQ2zgO\_kv%3Du4YtMaUMfZcj9MNJWC%3D\_MA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXar33evahvzhzbQ2zgO_kv%3Du4YtMaUMfZcj9MNJWC%3D_MA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Matias\_Waisgold](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@Matias\_Waisgold](https://discuss.elastic.co/u/Matias_Waisgold)\ **Post date:** [January 15, 2015, 8:07pm UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/7 "2015-01-15T20:07:12Z")
I'm on 1.4.1 and still seeing the same behavior. There should be a better practice than remove all shards at the same time and try to move a few. We are going to apply the same solution you mentioned, add more disk. Thank's for your help. 2015-01-15 16:09 GMT-03:00 Kimbro Staken [kstaken@kstaken.com](mailto:kstaken@kstaken.com): > So is this still happening with 1.4.2? > > Here's the ticket. Looks like the fix was supposed to be in 1.4.1 > > [disk.watermark.high relocates all shards creating a relocation storm · Issue #8538 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/8538) > > On Thu, Jan 15, 2015 at 10:55 AM, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) > wrote: > > > Great, thank you. We are creating another cluster with more disk space to > > avoid this situations. > > By any chance do you have the link to the issue? > > > > 2015-01-15 13:26 GMT-03:00 Kimbro Staken [kstaken@kstaken.com](mailto:kstaken@kstaken.com): > > > > > I've experienced what you're describing. I called it a "shard relocation > > > storm" and it's really tough to get under control. I opened a ticket on the > > > issue and a fix was supposedly included in 1.4.2. What version are you > > > running? > > > > > > If you want to truly manually manage this situation you could set > > > cluster.routing.allocation.disk.threshold\_enabled to false but that will > > > likely cause other issues. I ended up just setting > > > cluster.routing.allocation.disk.watermark.high to a really low value and > > > actively managed shard allocations to prevent nodes from getting anywhere > > > near that value. This is tricky as the way ES allocates shards it can > > > easily run nodes out of disk if you're regularly creating new indices and > > > those grow rapidly. > > > > > > Kimbro > > > > > > On Thu, Jan 15, 2015 at 6:14 AM, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) > > > wrote: > > > > > > > Yes, I've seen that but the problem is that when the threshold is > > > > reached it removes all shards from the server instead of just removing 1 > > > > and balance. And when that happens the cluster starts to move shards over > > > > everywhere and it never stops. > > > > > > > > Another problem we are having is that in the file storage we see data > > > > from shards that are not assigned to itself so it can´t allocate anything > > > > in this dirty state. > > > > > > > > 2015-01-15 0:09 GMT-03:00 Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com): > > > > > > > > > You could do this, but it's a lot of manual overhead to have to deal > > > > > with. > > > > > However ES does have some disk space awareness during allocation, take > > > > > a look at > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/index-modules-allocation.html#disk) > > > > > > > > > > On 15 January 2015 at 10:57, Matías Waisgold [mwaisgold@gmail.com](mailto:mwaisgold@gmail.com) > > > > > wrote: > > > > > > > > > > > Hi is there any setting that I can put to ES that it automatically > > > > > > assigns shards that are unassigned but never ever rebalance the cluster? > > > > > > I´ve found several issues when rebalancing and prefer to do it > > > > > > manually. > > > > > > If I set cluster.routing.allocation.enable to "none" nothing happens. > > > > > > If I set it to "all" then it starts rebalancing. > > > > > > > > > > > > Is it ok to combine cluster.routing.allocation.allow\_rebalance to > > > > > > "none" and cluster.routing.allocation.enable to "all". > > > > > > > > > > > > The issue is mainly because we are running low on disk and when that > > > > > > happens elasticsearch removes all shards from an instance, that doesn´t > > > > > > care about cluster.routing.allocation.cluster\_concurrent\_rebalance and > > > > > > starts moving shards like crazy around the entire cluster, filling the > > > > > > storage on other instances in the way that it will never stop balancing. > > > > > > > > > > > > Kind regards > > > > > > > > > > > > -- > > > > > > 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/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com) > > > > > > [https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/666a4d70-2497-4a2b-8c5e-774c7d0617b7%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > -- > > > > > You received this message because you are subscribed to a topic in the > > > > > Google Groups "elasticsearch" group. > > > > > To unsubscribe from this topic, visit > > > > > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe) > > > > > . > > > > > To unsubscribe from this group and all its topics, 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/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a\_Mgny75KkkKxRFP\_bJVhQL20bhR0UQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8KXKpmnAPWvr8a_Mgny75KkkKxRFP_bJVhQL20bhR0UQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > 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/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqFmk8t7couOmYEyPYNZPKepT8nKVrCM6fvSPW0CUjMwA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > > . > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe). > > > To unsubscribe from this group and all its topics, 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/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com) > > > [https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXaW8AdZJhGPGTRqD%3DYCSQ%2B2JdM-oGGpxkRgi0BZLOw2rg%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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/CAMaTqYq%2B\_S1\_CaPJ-\_HN8F%3DizX9VjKmF\_W5dhDFpAmS6kxw0WA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYq%2B_S1_CaPJ-_HN8F%3DizX9VjKmF_W5dhDFpAmS6kxw0WA%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAMaTqYq%2B\_S1\_CaPJ-\_HN8F%3DizX9VjKmF\_W5dhDFpAmS6kxw0WA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYq%2B_S1_CaPJ-_HN8F%3DizX9VjKmF_W5dhDFpAmS6kxw0WA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHqlig1M-T0/unsubscribe). > To unsubscribe from this group and all its topics, 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/CAA0DmXar33evahvzhzbQ2zgO\_kv%3Du4YtMaUMfZcj9MNJWC%3D\_MA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXar33evahvzhzbQ2zgO_kv%3Du4YtMaUMfZcj9MNJWC%3D_MA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAA0DmXar33evahvzhzbQ2zgO\_kv%3Du4YtMaUMfZcj9MNJWC%3D\_MA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXar33evahvzhzbQ2zgO_kv%3Du4YtMaUMfZcj9MNJWC%3D_MA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAMaTqYqTcALa3zKGVLXmobjbFkEMMR8L03xVR9r-1pBWsn451A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMaTqYqTcALa3zKGVLXmobjbFkEMMR8L03xVR9r-1pBWsn451A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:38am UTC](https://discuss.elastic.co/t/just-initialize-shards-when-problems-but-no-rebalance/21651/8 "2017-07-06T00:38:35Z")