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

Deleting a sub-shard in recovery state can mark parent shard as inactive

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.10.4, 5.5.2, 6.2
    • Fix Version/s: 6.2.1, 6.3, 7.0
    • Component/s: SolrCloud
    • Security Level: Public (Default Security Level. Issues are Public)
    • Labels:
      None

      Description

      When deleting a sub-shard after a failed split operation, the delete shard API unloads the replica cores and then deletes the shard state. But, say there were 2 replicas, if the following sequence occurs:

      1. 1st replica got deleted
      2. for any reason, the other replica published "state=active"

      Then the overseer can switch slice states and put parent shard as inactive and the sub-shards as active.

      We should defensively update sub-shard state back to "construction" and only then invoke the unload action on replica cores.

        Attachments

        1. SOLR-9455.patch
          2 kB
          Shalin Shekhar Mangar

          Issue Links

            Activity

              People

              • Assignee:
                shalinmangar Shalin Shekhar Mangar
                Reporter:
                shalinmangar Shalin Shekhar Mangar
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: