[jira] [Commented] (SOLR-5135) Deleting a collection should be extra aggressive in the face of failures.

["Mark Miller (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736374#comment-13736374 ] 

Mark Miller commented on SOLR-5135:
-----------------------------------

bq.  or create the collection again due

Seems you can actually create it again - we check existence vs the clusterstate.json rather than the /collections node - we should still remove the remnants though.
                
> Deleting a collection should be extra aggressive in the face of failures.
> -------------------------------------------------------------------------
>
>                 Key: SOLR-5135
>                 URL: https://issues.apache.org/jira/browse/SOLR-5135
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.5, 5.0
>
>
> Until Zk is the source of truth for the cluster, zk and local node states can get out of whack in certain situations - as a result, sometimes you cannot clean out all of the remnants of a collection to recreate it. For example, if the collection is listed in zk under /collections, but is not in clusterstate.json, you cannot remove or create the collection again due to a early exception in the collection removal chain.
> I think we should probably still return the error - but also delete as much as we can.

--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org