[
https://issues.apache.org/jira/browse/SOLR-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823012#comment-16823012
]
Ishan Chattopadhyaya commented on SOLR-13410:
---------------------------------------------
To summarise, when the prioritized overseer joined back (after a restart), all
other nodes, one by one, became overseer leader and gave up leadership, until
the prioritized overseer became the leader. During all this time, many overseer
messages kept failing, perhaps due to SOLR-13416.
> 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
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: overseerElection.log
>
>
> 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:
> # Setup solrcloud with 5 nodes, including one designated overseer
> # Restart overseer container
> Attached relevant logs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
