[
https://issues.apache.org/jira/browse/SOLR-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reopened SOLR-9455:
-----------------------------------------
Re-opened to back-port to 6.2.1
> Deleting a sub-shard in recovery state can mark parent shard as inactive
> ------------------------------------------------------------------------
>
> Key: SOLR-9455
> URL: https://issues.apache.org/jira/browse/SOLR-9455
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 4.10.4, 5.5.2, 6.2
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 6.2.1, 6.3, master (7.0)
>
> Attachments: SOLR-9455.patch
>
>
> 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:
> # 1st replica got deleted
> # 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
