# Why does node go into recovery after planned restart with allocation disabled

**URL:** <https://discuss.elastic.co/t/why-does-node-go-into-recovery-after-planned-restart-with-allocation-disabled/73991>\
**Category:** Elasticsearch\
**Created:** [February 5, 2017, 7:24pm UTC](https://discuss.elastic.co/t/why-does-node-go-into-recovery-after-planned-restart-with-allocation-disabled/73991 "2017-02-05T19:24:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jthoni](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@jthoni](https://discuss.elastic.co/u/jthoni)\
**Post date:** [February 5, 2017, 7:24pm UTC](https://discuss.elastic.co/t/why-does-node-go-into-recovery-after-planned-restart-with-allocation-disabled/73991/1 "2017-02-05T19:24:03Z")

</div>

We have to do period maintenance on our nodes that requires a restart of the box. When I do this, I set:  
"cluster.routing.allocation.enable" : "none"

Then I restart the box. When it is back, and the node has rejoined, I reenable allocation. At this point, I would expect the data on the node to still be good, and the only recovery to be the events that have queued while the box was down (a matter of a couple minutes). What I see is that when I reenable allocation, a long recovery cycle is kicked off. This means that updating all our nodes takes the entire day as I wait for green status before going on to the next node.

Thanks,  
~john

---

<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 5, 2017, 7:44pm UTC](https://discuss.elastic.co/t/why-does-node-go-into-recovery-after-planned-restart-with-allocation-disabled/73991/2 "2017-02-05T19:44:22Z")

</div>

What version are you on.

---

<div class="post-metadata">

**Author:** ![jthoni](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@jthoni](https://discuss.elastic.co/u/jthoni)\
**Post date:** [February 5, 2017, 8:07pm UTC](https://discuss.elastic.co/t/why-does-node-go-into-recovery-after-planned-restart-with-allocation-disabled/73991/3 "2017-02-05T20:07:55Z")

</div>

Sorry, 2.3.2

---

<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 5, 2017, 9:55pm UTC](https://discuss.elastic.co/t/why-does-node-go-into-recovery-after-planned-restart-with-allocation-disabled/73991/4 "2017-02-05T21:55:57Z")

</div>

Are you calling a [https://www.elastic.co/guide/en/elasticsearch/reference/2.4/indices-synced-flush.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/indices-synced-flush.html) before the restart?

---

<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:** [March 5, 2017, 9:56pm UTC](https://discuss.elastic.co/t/why-does-node-go-into-recovery-after-planned-restart-with-allocation-disabled/73991/5 "2017-03-05T21:56:10Z")

</div>

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