You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/08/27 03:40:21 UTC
[jira] [Commented] (SOLR-9439) Shard split clean up logic for older
failed splits is faulty
[ https://issues.apache.org/jira/browse/SOLR-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15440587#comment-15440587 ]
ASF subversion and git services commented on SOLR-9439:
-------------------------------------------------------
Commit 7d2f42e5436dc669cd48df8dafd45036bd6f9d76 in lucene-solr's branch refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=7d2f42e ]
SOLR-9439: Shard split clean up logic for older failed splits is faulty
> 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: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org