Description
Currently, when closed / cancelled, RecoveryStrategy can publish a recovery failed state. In a bad loop (like when no one can become leader because no one had a last state of active) this can cause very fast looped publishing of this state to zk.
It's an outstanding item to improve that specific scenario anyway, but regardless, we should fix the close / cancel path to never publish any state to zk.
Attachments
Attachments
Issue Links
- is related to
-
SOLR-5961 Solr gets crazy on /overseer/queue state change
- Closed
-
SOLR-7285 ActionThrottle will not pause if getNanoTime first returns 0.
- Closed
-
SOLR-8371 Try and prevent too many recovery requests from stacking up and clean up some faulty logic.
- Closed
- relates to
-
SOLR-7034 Consider allowing any node to become leader, regardless of their last published state.
- Closed