# Shard allocation after upgrade from 1.1.2 to 1.2.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [July 15, 2014, 2:03am UTC](https://discuss.elastic.co/t/shard-allocation-after-upgrade-from-1-1-2-to-1-2-2/18666 "2014-07-15T02:03:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Tommi\_Latti](https://avatars.discourse-cdn.com/v4/letter/t/ecc23a/32.png) [@Tommi\_Latti](https://discuss.elastic.co/u/Tommi_Latti)\ **Post date:** [July 15, 2014, 2:03am UTC](https://discuss.elastic.co/t/shard-allocation-after-upgrade-from-1-1-2-to-1-2-2/18666/1 "2014-07-15T02:03:51Z")
I have daily rotating indexes and everything usually balances out nicely. 8 shards plus 1 replica over 4 nodes goes nicely 4/4/4/4. All nodes are identical with the same ES settings. Now I checked the kopf plugin this morning to just check the status and I noticed that after the 1.2.2 upgrade the allocation for today's index is now 2/6/6/2 which is kinda weird. I know I could use the cluster api to move shards around but that's not fun to do every day and ES should know better. Anybody seeing something similar? [https://lh6.googleusercontent.com/-s4bZcjTYSDU/U8SL79zSThI/AAAAAAAAVqI/EO2P4TqrRwA/s1600/Screen+Shot+2014-07-15+at+10.50.39.png](https://lh6.googleusercontent.com/-s4bZcjTYSDU/U8SL79zSThI/AAAAAAAAVqI/EO2P4TqrRwA/s1600/Screen+Shot+2014-07-15+at+10.50.39.png) -- 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/0c308908-cf0f-4ba7-9d5b-d650265f8854%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0c308908-cf0f-4ba7-9d5b-d650265f8854%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![smonasco\_2](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@smonasco\_2](https://discuss.elastic.co/u/smonasco_2)\ **Post date:** [July 15, 2014, 3:35am UTC](https://discuss.elastic.co/t/shard-allocation-after-upgrade-from-1-1-2-to-1-2-2/18666/2 "2014-07-15T03:35:14Z")
[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html) There is a total shards per node feature that will allow you to force 4 per node and it can be set on live indexes. Not sure how you are creating your indexes but you can add that to the index during creation. -- 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/713ba841-20b3-49a7-a07a-ddb14a1eb6d5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/713ba841-20b3-49a7-a07a-ddb14a1eb6d5%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Tommi\_Latti](https://avatars.discourse-cdn.com/v4/letter/t/ecc23a/32.png) [@Tommi\_Latti](https://discuss.elastic.co/u/Tommi_Latti)\ **Post date:** [July 15, 2014, 5:31am UTC](https://discuss.elastic.co/t/shard-allocation-after-upgrade-from-1-1-2-to-1-2-2/18666/3 "2014-07-15T05:31:48Z")
That sounds like an idea πŸ™‚ My indexes get created dynamically around midnight, I'll check one more day and if it still looks this unbalanced, I'll put the settings in my template and see what happens. Thanks πŸ™‚ On Tuesday, 15 July 2014 12:35:14 UTC+9, smonasco wrote: > [Elasticsearch Platform β€” Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html) > > There is a total shards per node feature that will allow you to force 4 > per node and it can be set on live indexes. Not sure how you are creating > your indexes but you can add that to the index during creation. -- 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/abe56aaf-6788-4d10-9f27-c7cb924e5213%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/abe56aaf-6788-4d10-9f27-c7cb924e5213%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![smonasco\_2](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@smonasco\_2](https://discuss.elastic.co/u/smonasco_2)\ **Post date:** [July 15, 2014, 1:12pm UTC](https://discuss.elastic.co/t/shard-allocation-after-upgrade-from-1-1-2-to-1-2-2/18666/4 "2014-07-15T13:12:03Z")
No prob. On Jul 14, 2014 11:31 PM, "Tommi LΓ€tti" [sty@blosphere.net](mailto:sty@blosphere.net) wrote: > That sounds like an idea πŸ™‚ > > My indexes get created dynamically around midnight, I'll check one more > day and if it still looks this unbalanced, I'll put the settings in my > template and see what happens. > > Thanks πŸ™‚ > > On Tuesday, 15 July 2014 12:35:14 UTC+9, smonasco wrote: > > > [Elasticsearch Platform β€” Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/) > > reference/current/index-modules-allocation.html > > > > There is a total shards per node feature that will allow you to force 4 > > per node and it can be set on live indexes. Not sure how you are creating > > your indexes but you can add that to the index during creation. > > -- > 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/jk30RCL1KaQ/unsubscribe](https://groups.google.com/d/topic/elasticsearch/jk30RCL1KaQ/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/abe56aaf-6788-4d10-9f27-c7cb924e5213%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/abe56aaf-6788-4d10-9f27-c7cb924e5213%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/abe56aaf-6788-4d10-9f27-c7cb924e5213%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/abe56aaf-6788-4d10-9f27-c7cb924e5213%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/CAFDU5WJzXs-KWc%3DE0r4hrX%2Bcz\_%3D9mRSu4pXj5PTsYxB0aufT9g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAFDU5WJzXs-KWc%3DE0r4hrX%2Bcz_%3D9mRSu4pXj5PTsYxB0aufT9g%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:15am UTC](https://discuss.elastic.co/t/shard-allocation-after-upgrade-from-1-1-2-to-1-2-2/18666/5 "2017-07-06T01:15:42Z")
Closed on July 6, 2017, 1:15am UTC