[
https://issues.apache.org/jira/browse/SOLR-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410926#comment-17410926
]
Ishan Chattopadhyaya commented on SOLR-13444:
---------------------------------------------
I manually tested this scenario and wasn't able to reproduce it. Seems like
SOLR-13410 fixed it? I'm closing this issue, unless [~keshareenv] you feel this
is still a problem.
> Designated overseers not able to switch without at least one transition
> -----------------------------------------------------------------------
>
> Key: SOLR-13444
> URL: https://issues.apache.org/jira/browse/SOLR-13444
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: main (9.0)
> Reporter: Kesharee Nandan Vishwakarma
> Priority: Major
> Labels: overseer
> Attachments: SOLR-13410.patch
>
>
> This is related to another bug
> [SOLR-13410|https://issues.apache.org/jira/browse/SOLR-13410?focusedCommentId=16832041&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16832041]
> For a solrcloud setup with more than one designated overseer nodes, If we
> bring down one overseer node, there will be at least one transition overseer
> node before another designated node assumes overseer role. This is happening
> because OverseerNodePrioritizer is triggered once we have a new overseer node
> upon stopping a designated overseer leader node.
> Refer to 2 designated overseer nodes test case in
> testDesignatedOverseerRestarts#OverseerRolesTest in the patch to reproduce
> this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
