# Unequal shard allocaiton

**URL:** <https://discuss.elastic.co/t/unequal-shard-allocaiton/217284>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [January 31, 2020, 1:01am UTC](https://discuss.elastic.co/t/unequal-shard-allocaiton/217284 "2020-01-31T01:01:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijay\_kaali](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijay_kaali/32/59998_2.png) [@vijay\_kaali](https://discuss.elastic.co/u/vijay_kaali)\
**Post date:** [January 31, 2020, 1:01am UTC](https://discuss.elastic.co/t/unequal-shard-allocaiton/217284/1 "2020-01-31T01:01:10Z")

</div>

i have 8 data node elk and metricbeat configured with shard 2 replica 1. most of the times all of the shard is maximum spread in 3 node . in order to max performance i trying to create index with 5 shard replica 1 and doing a reindex . but i see all primary , replica created in just 3 nodes instead of using all nodes . 1st node has 4 shard , 2nd node 5 and 3rd node 1.

question is how can i ensure all my primary to be in different node so that my performance is better?  
out of 8 nodes 4 nodes have disk size 50% of remaining nodes . i.e 4 nodes have 1.5 tb and others have 3tb . is there problem on performance and unequal allocation

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 31, 2020, 6:06am UTC](https://discuss.elastic.co/t/unequal-shard-allocaiton/217284/2 "2020-01-31T06:06:48Z")

</div>

What is the output of `GET /_cat/nodes?v&h=id,ip,du,dup,v,r,m`?

---

<div class="post-metadata">

**Author:** ![vijay\_kaali](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijay_kaali/32/59998_2.png) [@vijay\_kaali](https://discuss.elastic.co/u/vijay_kaali)\
**Post date:** [January 31, 2020, 6:33am UTC](https://discuss.elastic.co/t/unequal-shard-allocaiton/217284/3 "2020-01-31T06:33:06Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> `GET /_cat/nodes?v&h=id,ip,du,dup,v,r,m` ?

id ip du dup v r  
PoPi 10.38.1.22 908.8gb 90.18 6.5.2 mdi  
XX1O 10.38.1.24 689.8gb 68.45 6.5.2 mdi  
OUcj 10.38.1.21 928.9gb 92.17 6.5.2 mdi  
bNap 10.38.0.35 2.1gb 0.72 6.5.2 i  
6aBT 10.38.0.37 67gb 67.11 6.5.2 i  
oQ96 10.38.0.33 1.9tb 99.09 6.5.2 mdi  
z-Mm 10.38.1.25 948.4gb 94.11 6.5.2 mdi  
6QD- 10.38.0.36 2.9gb 0.97 6.5.2 i  
wHZ5 10.38.0.32 1.8tb 92.04 6.5.2 mdi  
dq5d 10.38.0.34 1.8tb 91.96 6.5.2 mdi  
ixvx 10.38.1.23 804.6gb 79.85 6.5.2 mdi

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 31, 2020, 7:51am UTC](https://discuss.elastic.co/t/unequal-shard-allocaiton/217284/4 "2020-01-31T07:51:02Z")

</div>

What is the shard count per node? Do you have shards of very different sizes? How large is the largest shard?

---

<div class="post-metadata">

**Author:** ![vijay\_kaali](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijay_kaali/32/59998_2.png) [@vijay\_kaali](https://discuss.elastic.co/u/vijay_kaali)\
**Post date:** [January 31, 2020, 8:18am UTC](https://discuss.elastic.co/t/unequal-shard-allocaiton/217284/5 "2020-01-31T08:18:12Z")

</div>

we have 15 metric indexes each 550-600gb with 2 shards 1 replica and 6 rollup indexes less than 110gb same shard/replica set up

---

<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:** [February 28, 2020, 8:18am UTC](https://discuss.elastic.co/t/unequal-shard-allocaiton/217284/6 "2020-02-28T08:18:19Z")

</div>

Closed on February 28, 2020, 8:18am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
