[jira] [Assigned] (SOLR-13410) Designated overseer not able to become overseer quickly

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Assigned] (SOLR-13410) Designated overseer not able to become overseer quickly

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ishan Chattopadhyaya reassigned SOLR-13410:

    Assignee: Ishan Chattopadhyaya

> 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
> 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

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]