# Recovery after restart

**URL:** <https://discuss.elastic.co/t/recovery-after-restart/102426>\
**Category:** Elasticsearch\
**Created:** [October 2, 2017, 11:22am UTC](https://discuss.elastic.co/t/recovery-after-restart/102426 "2017-10-02T11:22:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![swan](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@swan](https://discuss.elastic.co/u/swan)\
**Post date:** [October 2, 2017, 11:22am UTC](https://discuss.elastic.co/t/recovery-after-restart/102426/1 "2017-10-02T11:22:42Z")

</div>

Hi guys,  
it seems it is a very common question but I did not manage to find the solution by myself.

I have a cluster with 5 nodes and restart of any of them triggers recovery. It is happening even if it is clean restart. Why do shards relocate from other nodes though all of them are available on the current node on the hard drive?

Is it ok? if it is so, could you please explain me why.  
If no, how to prevent relocation after node restart.

Befor restart I do:  
PUT \_cluster/settings  
{"transient" : {"cluster.routing.allocation.enable" : "none"}}

and have

PUT \_all/\_settings  
{"settings": {"index.unassigned.node\_left.delayed\_timeout": "15m"}}

and after:  
PUT \_cluster/settings  
{"transient" : {"cluster.routing.allocation.enable" : "all"}}

Thank you.

---

<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:** [October 30, 2017, 11:22am UTC](https://discuss.elastic.co/t/recovery-after-restart/102426/2 "2017-10-30T11:22:43Z")

</div>

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