# Elasticsearch rebalancing on single node

**URL:** https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274
**Category:** Elasticsearch
**Created:** [February 19, 2016, 8:10pm UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274 "2016-02-19T20:10:18Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Thomas\_Ardal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_ardal/32/7956_2.png) [@Thomas\_Ardal](https://discuss.elastic.co/u/Thomas_Ardal)
#### Post date: [February 19, 2016, 8:10pm UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274/1 "2016-02-19T20:10:18Z")

</div>

When running a single node setup, it always bugged me, that Elasticsearch uses a lot of time rebalancing all of the shards after a restart. The shards will always go to the same node as before restarting the node.

Is it recommended to set cluster.routing.rebalance.enable to none in single node clusters?

---

<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: [February 19, 2016, 11:25pm UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274/2 "2016-02-19T23:25:52Z")

</div>

Where are you seeing the rebalancing?  
It should be reallocating, because if you restart everything becomes unallocated, but that is it.

---

<div class="post-metadata">

### Author: ![Thomas\_Ardal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_ardal/32/7956_2.png) [@Thomas\_Ardal](https://discuss.elastic.co/u/Thomas_Ardal)
#### Post date: [February 20, 2016, 7:32am UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274/3 "2016-02-20T07:32:43Z")

</div>

Sorry, but I probably mean reallocating then. Why unallocate everything on shutdown and use time to reallocate on startup? The data is the same as when the node shut down and no new node is 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: [February 21, 2016, 7:22pm UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274/4 "2016-02-21T19:22:00Z")

</div>

What version are you on?  
It should be pretty quick if you are on 1.6 and above.

---

<div class="post-metadata">

### Author: ![Thomas\_Ardal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_ardal/32/7956_2.png) [@Thomas\_Ardal](https://discuss.elastic.co/u/Thomas_Ardal)
#### Post date: [February 22, 2016, 6:27am UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274/5 "2016-02-22T06:27:25Z")

</div>

You're right about the fact that it takes a long time on \< 1.6. But on 1.7.1 it still takes a couple of minutes with 4.000 shards.

---

<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: [February 22, 2016, 5:07pm UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274/6 "2016-02-22T17:07:19Z")

</div>

That's pretty quick for a lot of shards!

---

<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: [July 5, 2017, 11:14pm UTC](https://discuss.elastic.co/t/elasticsearch-rebalancing-on-single-node/42274/7 "2017-07-05T23:14:27Z")

</div>


