# ES Shard re-distribution problem

**URL:** <https://discuss.elastic.co/t/es-shard-re-distribution-problem/7385>\
**Category:** Elasticsearch\
**Created:** [April 18, 2012, 3:28pm UTC](https://discuss.elastic.co/t/es-shard-re-distribution-problem/7385 "2012-04-18T15:28:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nitish\_Sharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nitish_sharma/32/2626_2.png) [@Nitish\_Sharma](https://discuss.elastic.co/u/Nitish_Sharma)\
**Post date:** [April 18, 2012, 3:28pm UTC](https://discuss.elastic.co/t/es-shard-re-distribution-problem/7385/1 "2012-04-18T15:28:57Z")

</div>

Hi,  
I've a ES cluster of 4 nodes with 3 indices each having 10 shards and 2  
replicas. After indexing some data into it and running some performance  
tests, I realised 4 nodes may not be enough and added an additional node.  
In principle, every index should've (uniformly) re-distributed its shards.  
But, to my surprise, 2 indices have redistributed only 2 shards to this new  
node, while it should be 6 shards. And the third index has not transferred  
even a single shard to the new node. I dont think this is an expected  
behaviour from ES.  
Any pointers/suggestions?

Cheers  
Nitish

---

<div class="post-metadata">

**Author:** ![Berkay\_Mollamustafao](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Berkay\_Mollamustafao](https://discuss.elastic.co/u/Berkay_Mollamustafao)\
**Post date:** [April 18, 2012, 3:40pm UTC](https://discuss.elastic.co/t/es-shard-re-distribution-problem/7385/2 "2012-04-18T15:40:48Z")

</div>

Hi,

Shard distribution is not per index. It is based on total number of shards,  
so the behavior you see may be normal if the total number of shards per  
node is more or less even.  
There are some configuration options that you may be able to use to have a  
distribution that is more inline with your needs.

> **[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.

Regards,  
Berkay Mollamustafaoglu  
mberkay on yahoo, google and skype

On Wed, Apr 18, 2012 at 11:28 AM, Nitish Sharma  
[sharmanitishdutt@gmail.com](mailto:sharmanitishdutt@gmail.com)wrote:

> Hi,  
> I've a ES cluster of 4 nodes with 3 indices each having 10 shards and 2  
> replicas. After indexing some data into it and running some performance  
> tests, I realised 4 nodes may not be enough and added an additional node.  
> In principle, every index should've (uniformly) re-distributed its shards.  
> But, to my surprise, 2 indices have redistributed only 2 shards to this new  
> node, while it should be 6 shards. And the third index has not transferred  
> even a single shard to the new node. I dont think this is an expected  
> behaviour from ES.  
> Any pointers/suggestions?
> 
> Cheers  
> Nitish

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [April 19, 2012, 2:54pm UTC](https://discuss.elastic.co/t/es-shard-re-distribution-problem/7385/3 "2012-04-19T14:54:02Z")

</div>

Also note, we added the ability to set the number of shards per node for an  
index as an interim solution to force redistribution of shards, and we plan  
to improve on the allocation in the next version.

On Wed, Apr 18, 2012 at 6:40 PM, Berkay Mollamustafaoglu  
[mberkay@gmail.com](mailto:mberkay@gmail.com)wrote:

> Hi,
> 
> Shard distribution is not per index. It is based on total number of  
> shards, so the behavior you see may be normal if the total number of shards  
> per node is more or less even.  
> There are some configuration options that you may be able to use to have a  
> distribution that is more inline with your needs.  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/index-modules/allocation.html)
> 
> Regards,  
> Berkay Mollamustafaoglu  
> mberkay on yahoo, google and skype
> 
> On Wed, Apr 18, 2012 at 11:28 AM, Nitish Sharma \<  
> [sharmanitishdutt@gmail.com](mailto:sharmanitishdutt@gmail.com)\> wrote:
> 
> > Hi,  
> > I've a ES cluster of 4 nodes with 3 indices each having 10 shards and 2  
> > replicas. After indexing some data into it and running some performance  
> > tests, I realised 4 nodes may not be enough and added an additional node.  
> > In principle, every index should've (uniformly) re-distributed its shards.  
> > But, to my surprise, 2 indices have redistributed only 2 shards to this new  
> > node, while it should be 6 shards. And the third index has not transferred  
> > even a single shard to the new node. I dont think this is an expected  
> > behaviour from ES.  
> > Any pointers/suggestions?
> > 
> > Cheers  
> > Nitish

---

<div class="post-metadata">

**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, 3:31am UTC](https://discuss.elastic.co/t/es-shard-re-distribution-problem/7385/4 "2017-07-06T03:31:53Z")

</div>


