[
https://issues.apache.org/jira/browse/SOLR-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446679#comment-15446679
]
ASF subversion and git services commented on SOLR-9455:
-------------------------------------------------------
Commit 2700b952119feb2d53a163d3374f56c85a0de339 in lucene-solr's branch
refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2700b95 ]
SOLR-9455: Deleting a sub-shard in recovery state can mark parent shard as
inactive
> 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: master (7.0), 6.3
>
> 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]
