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

CLONE - Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.

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

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Duplicate
    • None
    • None
    • SolrCloud

    Description

      I'm doing this test
      collection test is replicated on two solr nodes running on 8983, 8984
      using external zk
      initially both nodes are empty

      1)turn on solr 8983
      2)add,commit a doc x con solr 8983
      3)turn off solr 8983
      4)turn on solr 8984
      5)shortly after (leader still not elected) turn on solr 8983
      6)8984 is elected as leader
      7)doc x is present on 8983 but not on 8984 (check issuing a query)

      In attachment are the solr.log files of both instances

      Attachments

        1. solr_8983.log
          38 kB
          Matteo Grolla
        2. solr_8984.log
          53 kB
          Matteo Grolla

        Issue Links

        Activity

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

          People

            markrmiller@gmail.com Mark Miller
            matteo.grolla Matteo Grolla
            Votes:
            2 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment