Kesharee Nandan Vishwakarma created SOLR-13410:
--------------------------------------------------
Summary: Designated overseer not able to become overseer quickly
Key: SOLR-13410
URL: https://issues.apache.org/jira/browse/SOLR-13410
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrCloud
Affects Versions: master (9.0)
Reporter: Kesharee Nandan Vishwakarma
Whenever a designated overseer node is restarted and overseer role is added
back if a designated node is not overseer leader following tasks take place:
1. one by one nodes from electionNodes list become leader and ask designated
node `to come join election at head`
2. current overseer node Fires Quit command and exits from Overseer Loop
3. Next node from `Overseer Loop` becomes leader repeats steps 1,2 until
designated overseer node becomes the leader
Problem with above flow: OverseerNodePrioritizer is not able to add `designated
node` at the head of electionNodes list
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
