# Shard distribution in Elasticsearch 1.4.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [December 21, 2014, 7:47pm UTC](https://discuss.elastic.co/t/shard-distribution-in-elasticsearch-1-4-2/21345 "2014-12-21T19:47:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![catwallader](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catwallader/32/1043_2.png) [@catwallader](https://discuss.elastic.co/u/catwallader)\ **Post date:** [December 21, 2014, 7:47pm UTC](https://discuss.elastic.co/t/shard-distribution-in-elasticsearch-1-4-2/21345/1 "2014-12-21T19:47:45Z")
I'm using a 4 node Elasticsearch cluster to ingest tweets from one of the public Twitter streams. After upgrading my from 1.3.2 to 1.4.2 I'm noticing an odd behavior with respect to how shards are distributed across the nodes. Whereas with 1.3.2 the 5 primary shards and 1 replica set of shards were evenly distributed across all 4 nodes, now I'm seeing this behavior: 1. All the primary shards are saved to one node 2. The replicas are split between two other nodes 3. The fourth node receives no shards at all I'm using default values for these settings: cluster.routing.allocation.balance.shard cluster.routing.allocation.balance.index cluster.routing.allocation.balance.primary cluster.routing.allocation.balance.threshold However I've set cluster.routing.allocation.balance.shard to 0.6f and cluster.routing.allocation.balance.primary to 0.06f in the hope that these settings will coerce Elasticsearch to distribute the shards more evenly. Has anyone else see this behavior? Is this a bug or a "feature"? -- 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/ed3f883d-fa7a-470c-96ba-513c8a8265ef%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ed3f883d-fa7a-470c-96ba-513c8a8265ef%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:** [December 21, 2014, 8:51pm UTC](https://discuss.elastic.co/t/shard-distribution-in-elasticsearch-1-4-2/21345/2 "2014-12-21T20:51:32Z")
I haven't seen it, but 1.4.2 has only just come out 🙂 Are you using Marvel at all? It might help shed some light on what is happening. Also just to confirm, did you restart all your nodes after the upgrade? Is there anything in the logs on each node that might be of use? On 21 December 2014 at 19:47, vic hargrave [vichargrave@gmail.com](mailto:vichargrave@gmail.com) wrote: > I'm using a 4 node Elasticsearch cluster to ingest tweets from one of the > public Twitter streams. After upgrading my from 1.3.2 to 1.4.2 I'm > noticing an odd behavior with respect to how shards are distributed across > the nodes. Whereas with 1.3.2 the 5 primary shards and 1 replica set of > shards were evenly distributed across all 4 nodes, now I'm seeing this > behavior: > > 1. All the primary shards are saved to one node > 2. The replicas are split between two other nodes > 3. The fourth node receives no shards at all > > I'm using default values for these settings: > > cluster.routing.allocation.balance.shard > cluster.routing.allocation.balance.index > cluster.routing.allocation.balance.primary > cluster.routing.allocation.balance.threshold > However I've set cluster.routing.allocation.balance.shard to 0.6f and > cluster.routing.allocation.balance.primary to 0.06f in the hope that > these settings will coerce Elasticsearch to distribute the shards more > evenly. > Has anyone else see this behavior? Is this a bug or a "feature"? > > -- > 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/ed3f883d-fa7a-470c-96ba-513c8a8265ef%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ed3f883d-fa7a-470c-96ba-513c8a8265ef%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/ed3f883d-fa7a-470c-96ba-513c8a8265ef%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ed3f883d-fa7a-470c-96ba-513c8a8265ef%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/CAEYi1X\_-pmny%2BDJVJ9j2%3D-%3DUJEMmPeh3Urx7TwhiTOS2e8z-vg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_-pmny%2BDJVJ9j2%3D-%3DUJEMmPeh3Urx7TwhiTOS2e8z-vg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![catwallader](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catwallader/32/1043_2.png) [@catwallader](https://discuss.elastic.co/u/catwallader)\ **Post date:** [December 21, 2014, 10:50pm UTC](https://discuss.elastic.co/t/shard-distribution-in-elasticsearch-1-4-2/21345/3 "2014-12-21T22:50:10Z")
Yes I did reboot the nodes after the upgrade and no there is nothing in the logs that would explain this. On Sunday, December 21, 2014 12:52:00 PM UTC-8, Mark Walkom wrote: > I haven't seen it, but 1.4.2 has only just come out 🙂 > > Are you using Marvel at all? It might help shed some light on what is > happening. > Also just to confirm, did you restart all your nodes after the upgrade? Is > there anything in the logs on each node that might be of use? > > On 21 December 2014 at 19:47, vic hargrave \<[vicha...@gmail.com](mailto:vicha...@gmail.com) > \\> wrote: > > > I'm using a 4 node Elasticsearch cluster to ingest tweets from one of the > > public Twitter streams. After upgrading my from 1.3.2 to 1.4.2 I'm > > noticing an odd behavior with respect to how shards are distributed across > > the nodes. Whereas with 1.3.2 the 5 primary shards and 1 replica set of > > shards were evenly distributed across all 4 nodes, now I'm seeing this > > behavior: > > > > 1. All the primary shards are saved to one node > > 2. The replicas are split between two other nodes > > 3. The fourth node receives no shards at all > > > > I'm using default values for these settings: > > > > cluster.routing.allocation.balance.shard > > cluster.routing.allocation.balance.index > > cluster.routing.allocation.balance.primary > > cluster.routing.allocation.balance.threshold > > However I've set cluster.routing.allocation.balance.shard to 0.6f and > > cluster.routing.allocation.balance.primary to 0.06f in the hope that > > these settings will coerce Elasticsearch to distribute the shards more > > evenly. > > Has anyone else see this behavior? Is this a bug or a "feature"? > > > > -- > > 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/ed3f883d-fa7a-470c-96ba-513c8a8265ef%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ed3f883d-fa7a-470c-96ba-513c8a8265ef%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/ed3f883d-fa7a-470c-96ba-513c8a8265ef%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ed3f883d-fa7a-470c-96ba-513c8a8265ef%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/5c2102aa-1a7f-4012-a9fc-f0cb4ce34963%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5c2102aa-1a7f-4012-a9fc-f0cb4ce34963%40googlegroups.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:42am UTC](https://discuss.elastic.co/t/shard-distribution-in-elasticsearch-1-4-2/21345/4 "2017-07-06T00:42:27Z")