[SOLR-13410] Designated overseer not able to become overseer quickly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 9.0
• Fix Version/s: 7.7.2, 8.1
• Component/s: SolrCloud
• Assignee: Ishan Chattopadhyaya
• Reporter: Kesharee Nandan Vishwakarma
• Created: 17/Apr/19 08:08
• Updated: 12/May/22 14:33
• Resolved: 06/May/19 19:31

Description

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

Steps to reproduce:

1. Setup solrcloud with 5 nodes, including one designated overseer
2. Restart overseer container

Attached relevant logs

Issue Links

• causes: SOLR-16145 Overseer rejoinOverseerElection NPE