[
https://issues.apache.org/jira/browse/SOLR-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13444:
-----------------------------------------------
Description:
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.
was:
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, there will
be at least one transition overseer node before a 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.
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: master (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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
