# Shard rebalancing after node restart

**URL:** <https://discuss.elastic.co/t/shard-rebalancing-after-node-restart/26130>\
**Category:** Elasticsearch\
**Created:** [July 23, 2015, 7:27am UTC](https://discuss.elastic.co/t/shard-rebalancing-after-node-restart/26130 "2015-07-23T07:27:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![debayan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/debayan/32/44770_2.png) [@debayan](https://discuss.elastic.co/u/debayan)\
**Post date:** [July 23, 2015, 7:27am UTC](https://discuss.elastic.co/t/shard-rebalancing-after-node-restart/26130/1 "2015-07-23T07:27:24Z")

</div>

Hi,

I have a 4 node cluster. When I restart one of these nodes it seems to sync all the shards it originally had from the other nodes. This is inspite the fact that this node has most of the data already on disk.

How can I stop such massive data transfer from other nodes and instead ask the restarted node to take most of the data from its own disk, and then do sync for data that does not exist on it?

---

<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:** [July 23, 2015, 7:28am UTC](https://discuss.elastic.co/t/shard-rebalancing-after-node-restart/26130/2 "2015-07-23T07:28:06Z")

</div>

Upgrade to ES 1.6.0, there are improvements to help this (shard flushing) 🙂

---

<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:59pm UTC](https://discuss.elastic.co/t/shard-rebalancing-after-node-restart/26130/3 "2017-07-05T23:59:41Z")

</div>


