[SOLR-9455] Deleting a sub-shard in recovery state can mark parent shard as inactive

• 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
• Assignee: Shalin Shekhar Mangar
• Reporter: Shalin Shekhar Mangar
• Created: 29/Aug/16 16:21
• Updated: 02/Oct/19 17:24
• Resolved: 12/Sep/16 11:56

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.

Issue Links

• relates to: SOLR-9438 Shard split can lose data