[
https://issues.apache.org/jira/browse/SOLR-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765229#comment-13765229
]
ASF subversion and git services commented on SOLR-5233:
-------------------------------------------------------
Commit 1522465 from [email protected] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1522465 ]
SOLR-5233: The deleteshard collections API doesn't wait for cluster state to
update, can fail if some nodes of the deleted shard were down and had incorrect
logging.
> admin/collections?action=DELETESHARD broken
> -------------------------------------------
>
> Key: SOLR-5233
> URL: https://issues.apache.org/jira/browse/SOLR-5233
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.4
> Reporter: Christine Poerschke
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-5233.patch
>
>
> The problem we saw was that deleting a shard did not actually delete it,
> although it semi-claimed to have done so.
> {noformat}
> ...
> o.a.s.c.OverseerCollectionProcessor [OverseerCollectionProcessor.java:723]
> Delete shard invoked
> ...
> o.a.s.c.OverseerCollectionProcessor [OverseerCollectionProcessor.java:781]
> Successfully deleted collection collection1, shard: null
> ...
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
