[
https://issues.apache.org/jira/browse/SOLR-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791806#comment-13791806
]
Mark Miller commented on SOLR-5135:
-----------------------------------
Sure, just remove the /collection/{name} node manually. You can use the zk cmd
line tools, the zkcli tool, or a graphical tool (I like the zk eclipse plugin).
> 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
>
> Attachments: SOLR-5135.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
