[
https://issues.apache.org/jira/browse/SOLR-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831862#comment-16831862
]
Ishan Chattopadhyaya commented on SOLR-13410:
---------------------------------------------
[~keshareenv], sounds like a good idea for a test! This is usually the most
important user facing scenario. I don't have the bandwidth currently, but would
be great if you can please write it up.
Here are the observations that led to the patch:
# The prioritized overseer wasn't actually re-joining at the head. It was
supposed have happened due to
https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/cloud/OverseerNodePrioritizer.java#L92-L97,
but those two lines had absolutely no effect on the overseer queue.
# The reason seemed to be that this condition was always false and as a result,
that function did nothing.
https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/cloud/ZkController.java#L2142
Since that part of the code was introduced in SOLR-6095, I would like to
request a review from [~noble.paul], [~shalinmangar].
> 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: SOLR-13410.patch, SOLR-13410.patch, 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]
