# Primary shadrs allocated in one node alone

**URL:** https://discuss.elastic.co/t/primary-shadrs-allocated-in-one-node-alone/77621
**Category:** Elasticsearch
**Created:** [March 7, 2017, 9:26am UTC](https://discuss.elastic.co/t/primary-shadrs-allocated-in-one-node-alone/77621 "2017-03-07T09:26:30Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![kishorramanan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kishorramanan/32/12823_2.png) [@kishorramanan](https://discuss.elastic.co/u/kishorramanan)
#### Post date: [March 7, 2017, 9:26am UTC](https://discuss.elastic.co/t/primary-shadrs-allocated-in-one-node-alone/77621/1 "2017-03-07T09:26:30Z")

</div>

When I bought down one node for a config update and relaunched it, the Primary shards are assigned only to the node with was online during update.

Should I make the secondary node shards as primary? If so how do I do it?

Tried:

```
/_cluster/settings -d '{
    "transient" : {
        "cluster.routing.allocation.enable" : "primaries"
    }
}'

```

and

```
/_cluster/settings -d '{
    "transient" : {
        "cluster.routing.allocation.enable" : "all"
    }
}'

```

ES version: 2.4 (Contianerized ES)

 ![](https://us1.discourse-cdn.com/elastic/original/3X/d/1/d1437b65e2a009b806ed1109ad385e769f1278cb.png)

---

<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: [April 4, 2017, 9:27am UTC](https://discuss.elastic.co/t/primary-shadrs-allocated-in-one-node-alone/77621/2 "2017-04-04T09:27:33Z")

</div>

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