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

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.


What version are you on.

Sorry, 2.3.2

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

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