# After upgrading to Elasticsearch 6 all primary shards are going to one server?

**URL:** <https://discuss.elastic.co/t/after-upgrading-to-elasticsearch-6-all-primary-shards-are-going-to-one-server/108172>\
**Category:** Elasticsearch\
**Created:** [November 17, 2017, 5:01pm UTC](https://discuss.elastic.co/t/after-upgrading-to-elasticsearch-6-all-primary-shards-are-going-to-one-server/108172 "2017-11-17T17:01:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Warren\_Turner](https://avatars.discourse-cdn.com/v4/letter/w/e9c0ed/32.png) [@Warren\_Turner](https://discuss.elastic.co/u/Warren_Turner)\
**Post date:** [November 17, 2017, 5:01pm UTC](https://discuss.elastic.co/t/after-upgrading-to-elasticsearch-6-all-primary-shards-are-going-to-one-server/108172/1 "2017-11-17T17:01:24Z")

</div>

Hey Everybody! (I'm having lots of fun with Elastic 6 if you all can't tell from all my posts :P)

So my Elastic 6 cluster works, but it is doing this odd thing where when a new index is created it puts all the primary shards on one node? So for example, I have 3 nodes and 5 shards per index:

Node 1: Replica shards 1, 2, 3  
Node 2: Replica shards 4, 5  
Node 3: Primary shards 1, 2, 3, 4, 5

That doesn't seem very balanced to me? Is there a new setting I need for this?

---

<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:** [November 18, 2017, 9:20am UTC](https://discuss.elastic.co/t/after-upgrading-to-elasticsearch-6-all-primary-shards-are-going-to-one-server/108172/2 "2017-11-18T09:20:10Z")

</div>

Is that the only index you have in the cluster?

---

<div class="post-metadata">

**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:** [November 18, 2017, 9:58am UTC](https://discuss.elastic.co/t/after-upgrading-to-elasticsearch-6-all-primary-shards-are-going-to-one-server/108172/3 "2017-11-18T09:58:39Z")

</div>

Elasticsearch doesn't distinguish between primary and replica when allocating (unless you tell it to with allocation filtering/awareness). It just looks at pure shard count.

---

<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:** [December 16, 2017, 9:59am UTC](https://discuss.elastic.co/t/after-upgrading-to-elasticsearch-6-all-primary-shards-are-going-to-one-server/108172/4 "2017-12-16T09:59:30Z")

</div>

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