# Cluster Routing Allocation Settings

**URL:** <https://discuss.elastic.co/t/cluster-routing-allocation-settings/71045>\
**Category:** Elasticsearch\
**Created:** [January 10, 2017, 9:46am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-settings/71045 "2017-01-10T09:46:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xavier.tiendeo](https://avatars.discourse-cdn.com/v4/letter/x/e8c25b/32.png) [@xavier.tiendeo](https://discuss.elastic.co/u/xavier.tiendeo)\
**Post date:** [January 10, 2017, 9:46am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-settings/71045/1 "2017-01-10T09:46:15Z")

</div>

We have a cluster of two nodes (ES 2.2), indexes have one replica so all shards are in both nodes. If we restart a node, all shards in that node are set as unasigned, we think this can be resolved with

"transient": {  
"cluster": {  
"routing": {  
"allocation": {  
"enable": "none"

but we don't understand the meaning of another parameter disable\_allocation": "false"? is from another version?

how can then reset transient settings?

thanks

---

<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:** [January 12, 2017, 6:33am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-settings/71045/2 "2017-01-12T06:33:58Z")

</div>

> [@xavier.tiendeo](#):
>
> If we restart a node, all shards in that node are set as unasigned, we think this can be resolved with

It won't _prevent_ that, you will still have half of your shards unassigned.

> [@xavier.tiendeo](#):
>
> but we don't understand the meaning of another parameter disable\_allocation": "false"? is from another version?

It's the same thing, just an older variant/

> [@xavier.tiendeo](#):
>
> how can then reset transient settings?

That's difficult until 5.X, so you should upgrade.

---

<div class="post-metadata">

**Author:** ![xavier.tiendeo](https://avatars.discourse-cdn.com/v4/letter/x/e8c25b/32.png) [@xavier.tiendeo](https://discuss.elastic.co/u/xavier.tiendeo)\
**Post date:** [January 12, 2017, 9:06am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-settings/71045/3 "2017-01-12T09:06:54Z")

</div>

Thansk for the response, can we prevent " all shards in that node are set as unasigned" in another way?  
so we have no shards unassigned, or at least a big % of them?

---

<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:** [January 12, 2017, 9:46am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-settings/71045/4 "2017-01-12T09:46:37Z")

</div>

Don't shut down the node, or add more nodes.

---

<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 9, 2017, 9:47am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-settings/71045/5 "2017-02-09T09:47:08Z")

</div>

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