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

Assign.buildCoreName can lead to error in creating a new core when legacyCloud=false

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.1, master (8.0)
    • Component/s: None
    • Security Level: Public (Default Security Level. Issues are Public)
    • Labels:
      None

      Description

      Here are the case

      shard1 : {
          node1 : shard1_replica1,
          node2 : shard1_replica2
      }
      

      node2 go down, autoAddReplicasPlanAction is executed

      shard1 : {
          node1 : shard1_replica1,
          node3 : shard1_replica3
      }
      

      node2 back alive, because shard1_replica2 is removed from states.json so that core won't be loaded ( but it won't be removed neither ). Then node1 go down, Assign.buildCoreName will create a core with name=shard1_replica2 which lead to a failure.

        Attachments

        1. SOLR-11011.2.patch
          29 kB
          Cao Manh Dat
        2. SOLR-11011.2.patch
          25 kB
          Cao Manh Dat
        3. SOLR-11011.3.patch
          7 kB
          Cao Manh Dat
        4. SOLR-11011.patch
          24 kB
          Cao Manh Dat
        5. SOLR-11011.patch
          23 kB
          Cao Manh Dat
        6. SOLR-11011.patch
          24 kB
          Cao Manh Dat
        7. SOLR-11011.patch
          9 kB
          Cao Manh Dat

          Issue Links

            Activity

              People

              • Assignee:
                caomanhdat Cao Manh Dat
                Reporter:
                caomanhdat Cao Manh Dat
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: