# One node one primary shard

**URL:** <https://discuss.elastic.co/t/one-node-one-primary-shard/282066>\
**Category:** Elasticsearch\
**Created:** [August 20, 2021, 10:41am UTC](https://discuss.elastic.co/t/one-node-one-primary-shard/282066 "2021-08-20T10:41:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![terrainc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/terrainc/32/81564_2.png) [@terrainc](https://discuss.elastic.co/u/terrainc)\
**Post date:** [August 20, 2021, 10:41am UTC](https://discuss.elastic.co/t/one-node-one-primary-shard/282066/1 "2021-08-20T10:41:56Z")

</div>

I have 6 nodes and 6 primary shards for each index plus replica.  
I want to be sure that each index primary shard got own node.  
How I understand, this can be controlled by allocation.balance

```auto
      "cluster.routing.allocation.balance.shard": 0.05,
      "cluster.routing.allocation.balance.index": 0.95,
      "cluster.routing.allocation.balance.threshold": 0.95,

```

But looks like this settings work with primary and replica shards. As result I am getting the following:

 ![Screenshot 2021-08-20 at 13.36.18](https://us1.discourse-cdn.com/elastic/original/3X/b/4/b4084f5d208afc2201b0477abadd1a76b6031436.png)  
Here one problem. Due ILM policy after few days replica will be dropped. And after replica dropped - rebalance will start and move shard 0 or 5 to node es-logs-1-1. Meaningless operation. Is any way to do not allow this kind of spread?

---

<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:** [September 17, 2021, 10:42am UTC](https://discuss.elastic.co/t/one-node-one-primary-shard/282066/2 "2021-09-17T10:42:38Z")

</div>

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