What are the benefits/drawbacks to using
cluster.routing.allocation.enable when doing a rolling restart?
From what I understand:
- Prevents ES from triggering allocation
- It also has the benefit of cancelling allocation if timeout expires
cluster.routing.allocation.enable: none(or new_primaries)
- Prevents allocation of new primaries
It seems as though when doing a rolling restart you'd want to increase the node_left.delayed_timeout (Default 1m) to something reasonable (5m for us) or something pretty high for manual maintenance (2h?). Yet the docs for rolling restarts recommend setting allocation enable to none (which should really be new_primaries...).
Am I missing something or over simplifying?