[
https://issues.apache.org/jira/browse/SOLR-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448710#comment-15448710
]
Shalin Shekhar Mangar commented on SOLR-9439:
---------------------------------------------
Actually all the fixes that I had done in this issue are not necessary if the
deleteshard API can internally call delete replica API which does the right
thing. Now that we have a parallel mode for the delete replica API, we can just
invoke it and then clear the slice from the cluster state. I'll put up a patch.
> Shard split clean up logic for older failed splits is faulty
> ------------------------------------------------------------
>
> Key: SOLR-9439
> URL: https://issues.apache.org/jira/browse/SOLR-9439
> 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.1
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: master (7.0), 6.3
>
> Attachments: Lucene-Solr-tests-master.8015.log.gz, SOLR-9439.patch,
> SOLR-9439.patch, SOLR-9439.patch
>
>
> In case a split finds that previous sub-shards exist in construction or
> recovery state. it tries to clean them up by invoking deleteshard API.
> However, the clean up logic tries to invoke deleteshard on the same
> sub-shards as many times as the requested number of sub-ranges. Such repeat
> calls to deleteshard fail and therefore fail the entire shard split operation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
