Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-13410

Designated overseer not able to become overseer quickly

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: master (9.0)
    • Fix Version/s: 7.7.2, 8.1
    • Component/s: SolrCloud
    • Labels:
      None

      Description

      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:

      1. Setup solrcloud with 5 nodes, including one designated overseer
      2. Restart overseer container

      Attached relevant logs

        Attachments

        1. SOLR-13410.patch
          4 kB
          Kesharee Nandan Vishwakarma
        2. SOLR-13410.patch
          9 kB
          Kesharee Nandan Vishwakarma
        3. SOLR-13410.patch
          8 kB
          Ishan Chattopadhyaya
        4. SOLR-13410.patch
          6 kB
          Ishan Chattopadhyaya
        5. overseerElection.log
          13 kB
          Kesharee Nandan Vishwakarma

          Activity

            People

            • Assignee:
              ichattopadhyaya Ishan Chattopadhyaya
              Reporter:
              keshareenv Kesharee Nandan Vishwakarma
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: