# When does ElasticSearch reallocate shards between nodes? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 21, 2014, 6:26am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383 "2014-08-21T06:26:34Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ElasticSearch\_Users\_](https://avatars.discourse-cdn.com/v4/letter/e/b4bc9f/32.png) [@ElasticSearch\_Users\_](https://discuss.elastic.co/u/ElasticSearch_Users_)\ **Post date:** [August 21, 2014, 6:26am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383/1 "2014-08-21T06:26:34Z")
Hi, What can be the possible causes when ElasticSearch will automatically reallocate a shard from node in the cluster to another node? One can be obviously when you add a new node. What are the automatic triggers, like continuously indexing new data or something? What is the policy for this? Thanks, Sandeep -- 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/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 21, 2014, 7:14am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383/2 "2014-08-21T07:14:49Z")
There is a formula ES uses by default to find if nodes get unbalanced regarding the shards. See > **[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. Jörg On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via elasticsearch [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) wrote: > Hi, > > What can be the possible causes when Elasticsearch will automatically > reallocate a shard from node in the cluster to another node? > > One can be obviously when you add a new node. > > What are the automatic triggers, like continuously indexing new data or > something? What is the policy for this? > > Thanks, > Sandeep > > -- > 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/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%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/CAKdsXoFrPFkgN8QkTDx6B%2Bq-3joicvMGB%2Bxj9vAtF4zeDoHPfg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFrPFkgN8QkTDx6B%2Bq-3joicvMGB%2Bxj9vAtF4zeDoHPfg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![ElasticSearch\_Users\_](https://avatars.discourse-cdn.com/v4/letter/e/b4bc9f/32.png) [@ElasticSearch\_Users\_](https://discuss.elastic.co/u/ElasticSearch_Users_)\ **Post date:** [August 21, 2014, 7:57am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383/3 "2014-08-21T07:57:48Z")
Hi Jorg, Thanks. Is there a size based allocation. What seems to be is that we have allocation based on number of primaries, per index, per node, etc. Is there a size factor that comes into play like, say if the routing is not even function, and shards on one node are more heavily loaded than another? Thanks, Sandeep On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote: > There is a formula ES uses by default to find if nodes get unbalanced > regarding the shards. See > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#_balanced_shards) > > Jörg > > On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via > elasticsearch \<[elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) \\> wrote: > > > Hi, > > > > What can be the possible causes when Elasticsearch will automatically > > reallocate a shard from node in the cluster to another node? > > > > One can be obviously when you add a new node. > > > > What are the automatic triggers, like continuously indexing new data or > > something? What is the policy for this? > > > > Thanks, > > Sandeep > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%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/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 21, 2014, 8:19am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383/4 "2014-08-21T08:19:47Z")
There is disk-based allocation. It does not take shard volume into account. It is not always a good idea to use total shard volume per node as a measurement across indices, consider heavy bulk indexing with steep volume changes, but the remaining disk space. > **[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. If you mean search load by "heavily loaded", I suggest to just add replica, maybe auto expand replica, so each node holds every shard as a copy, for best load balancing. Jörg On Thu, Aug 21, 2014 at 9:57 AM, 'Sandeep Ramesh Khanzode' via elasticsearch [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) wrote: > Hi Jorg, > > Thanks. Is there a size based allocation. What seems to be is that we have > allocation based on number of primaries, per index, per node, etc. Is there > a size factor that comes into play like, say if the routing is not even > function, and shards on one node are more heavily loaded than another? > > Thanks, > Sandeep > > On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote: > > > There is a formula ES uses by default to find if nodes get unbalanced > > regarding the shards. See > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/) > > reference/current/cluster-update-settings.html#\_balanced\_shards > > > > Jörg > > > > On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via > > elasticsearch [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) wrote: > > > > > Hi, > > > > > > What can be the possible causes when Elasticsearch will automatically > > > reallocate a shard from node in the cluster to another node? > > > > > > One can be obviously when you add a new node. > > > > > > What are the automatic triggers, like continuously indexing new data or > > > something? What is the policy for this? > > > > > > Thanks, > > > Sandeep > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%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/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%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/CAKdsXoG9kRDhd22oJ20Q8MSzDancbn67aNn89uADWovX3A11iw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG9kRDhd22oJ20Q8MSzDancbn67aNn89uADWovX3A11iw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![ElasticSearch\_Users\_](https://avatars.discourse-cdn.com/v4/letter/e/b4bc9f/32.png) [@ElasticSearch\_Users\_](https://discuss.elastic.co/u/ElasticSearch_Users_)\ **Post date:** [August 21, 2014, 8:26am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383/5 "2014-08-21T08:26:49Z")
I see what you mean. Is it possible that once the shards have been allocated by this formula or the policies, they will ever change again. I mean, if we have 3 indices on a two node cluster with 10 shards each. Now I add another index with 10 shards, will the EXISTING indices' shards be reallocated? Or is reallocation only for new shards? On Thursday, 21 August 2014 13:49:54 UTC+5:30, Jörg Prante wrote: > There is disk-based allocation. It does not take shard volume into > account. It is not always a good idea to use total shard volume per node as > a measurement across indices, consider heavy bulk indexing with steep > volume changes, but the remaining disk space. > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk) > > If you mean search load by "heavily loaded", I suggest to just add > replica, maybe auto expand replica, so each node holds every shard as a > copy, for best load balancing. > > Jörg > > On Thu, Aug 21, 2014 at 9:57 AM, 'Sandeep Ramesh Khanzode' via > elasticsearch \<[elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) \\> wrote: > > > Hi Jorg, > > > > Thanks. Is there a size based allocation. What seems to be is that we > > have allocation based on number of primaries, per index, per node, etc. Is > > there a size factor that comes into play like, say if the routing is not > > even function, and shards on one node are more heavily loaded than another? > > > > Thanks, > > Sandeep > > > > On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote: > > > > > There is a formula ES uses by default to find if nodes get unbalanced > > > regarding the shards. See > > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/) > > > reference/current/cluster-update-settings.html#\_balanced\_shards > > > > > > Jörg > > > > > > On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via > > > elasticsearch [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) wrote: > > > > > > > Hi, > > > > > > > > What can be the possible causes when Elasticsearch will automatically > > > > reallocate a shard from node in the cluster to another node? > > > > > > > > One can be obviously when you add a new node. > > > > > > > > What are the automatic triggers, like continuously indexing new data or > > > > something? What is the policy for this? > > > > > > > > Thanks, > > > > Sandeep > > > > > > > > -- > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%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/f0f8129c-d61a-4a54-bf98-ce386846b194%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f0f8129c-d61a-4a54-bf98-ce386846b194%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 21, 2014, 9:51am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383/6 "2014-08-21T09:51:36Z")
By default, also existing shards will be reallocated. You can also move shards around as you like but I do not recommend it if you do it just for fun. ES default setting for shard allocation is very good. > **[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. Jörg On Thu, Aug 21, 2014 at 10:26 AM, 'Sandeep Ramesh Khanzode' via elasticsearch [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) wrote: > I see what you mean. > > Is it possible that once the shards have been allocated by this formula or > the policies, they will ever change again. > > I mean, if we have 3 indices on a two node cluster with 10 shards each. > Now I add another index with 10 shards, will the EXISTING indices' shards > be reallocated? Or is reallocation only for new shards? > > On Thursday, 21 August 2014 13:49:54 UTC+5:30, Jörg Prante wrote: > > > There is disk-based allocation. It does not take shard volume into > > account. It is not always a good idea to use total shard volume per node as > > a measurement across indices, consider heavy bulk indexing with steep > > volume changes, but the remaining disk space. > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/) > > reference/current/index-modules-allocation.html#disk > > > > If you mean search load by "heavily loaded", I suggest to just add > > replica, maybe auto expand replica, so each node holds every shard as a > > copy, for best load balancing. > > > > Jörg > > > > On Thu, Aug 21, 2014 at 9:57 AM, 'Sandeep Ramesh Khanzode' via > > elasticsearch [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) wrote: > > > > > Hi Jorg, > > > > > > Thanks. Is there a size based allocation. What seems to be is that we > > > have allocation based on number of primaries, per index, per node, etc. Is > > > there a size factor that comes into play like, say if the routing is not > > > even function, and shards on one node are more heavily loaded than another? > > > > > > Thanks, > > > Sandeep > > > > > > On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote: > > > > > > > There is a formula ES uses by default to find if nodes get unbalanced > > > > regarding the shards. See > > > > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/referenc) > > > > e/current/cluster-update-settings.html#\_balanced\_shards > > > > > > > > Jörg > > > > > > > > On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via > > > > elasticsearch [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) wrote: > > > > > > > > > Hi, > > > > > > > > > > What can be the possible causes when Elasticsearch will automatically > > > > > reallocate a shard from node in the cluster to another node? > > > > > > > > > > One can be obviously when you add a new node. > > > > > > > > > > What are the automatic triggers, like continuously indexing new data > > > > > or something? What is the policy for this? > > > > > > > > > > Thanks, > > > > > Sandeep > > > > > > > > > > -- > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40goo > > > > > [glegroups.com](http://glegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e4569cb1-f33a-41ab-9598-ec5e0c7ef7b5%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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6362f730-1ecd-4ffc-b1ef-fe4f343781c4%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/f0f8129c-d61a-4a54-bf98-ce386846b194%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f0f8129c-d61a-4a54-bf98-ce386846b194%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/f0f8129c-d61a-4a54-bf98-ce386846b194%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f0f8129c-d61a-4a54-bf98-ce386846b194%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/CAKdsXoGHQ\_WSOpX7za65NnGPzHTeMxEhv0d03N0ZVswx4zZWRQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGHQ_WSOpX7za65NnGPzHTeMxEhv0d03N0ZVswx4zZWRQ%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, 1:07am UTC](https://discuss.elastic.co/t/when-does-elasticsearch-reallocate-shards-between-nodes/19383/7 "2017-07-06T01:07:13Z")