[
https://issues.apache.org/jira/browse/SOLR-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-5233:
----------------------------------------
Attachment: SOLR-5233.patch
# Used constants everywhere to avoid passing wrong parameters.
# Fixed logging in OverseerCollectionProcessor
The deleteshard succeeds even without this patch because a shard is deleted if
all cores are unloaded. It can fail without this patch if some cores were down.
Also, without this patch, the wait logic in OverseerCollectionProcessor was
wrong and didn't actually wait for the cluster state to update.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
