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

When we are starting a shard from rest, a leader should not consider it's last published state when deciding if it can be the new leader.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1, 6.0
    • Component/s: SolrCloud
    • Labels:
      None

      Description

      This makes it so that if a leader goes down before any replicas sync from it, one of the replicas won't take over. But because we wait a while for known replicas to come up and sync + pick the best leader, we should not need to be so strict in this protection and let a replica take a stab at being the leader - it may have been up to date and was only publishing through recovery phases to find that out.

        Attachments

          Activity

            People

            • Assignee:
              markrmiller@gmail.com Mark Miller
              Reporter:
              markrmiller@gmail.com Mark Miller
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: