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

Leader Initiated Recovery should not stop a leader that participated in an election with all of it's replicas from becoming a valid leader.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 5.4, 6.0
    • None
    • None

    Description

      Currently, because of SOLR-8069, all the replicas in a shard can be put into LIR.

      If you restart such a shard, the valid leader will will win the election and sync with the shard and then be blocked from registering as ACTIVE because it is in LIR.

      I think that is a little wonky because I don't think it even tries another candidate because the leader that cannot publish ACTIVE does not have it's election canceled.

      While SOLR-8069 should prevent this situation, we should add logic to allow a leader that can sync with it's full shard to become leader and publish ACTIVE regardless of LIR.

      Attachments

        1. SOLR-8075.patch
          3 kB
          Mark Miller
        2. SOLR-8075.patch
          7 kB
          Mark Miller
        3. SOLR-8075.patch
          7 kB
          Mark Miller
        4. SOLR-8075.patch
          8 kB
          Mark Miller
        5. SOLR-8075.patch
          5 kB
          Mark Miller
        6. SOLR-8075.patch
          8 kB
          Mark Miller
        7. SOLR-8075.patch
          8 kB
          Mark Miller

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            markrmiller@gmail.com Mark Miller
            markrmiller@gmail.com Mark Miller
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment