[
https://issues.apache.org/jira/browse/SOLR-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter resolved SOLR-6639.
----------------------------------
Resolution: Duplicate
I think this is a dupe of SOLR-6232. I tried to create a new collection named
"foo" that had a problem in the solrconfig.xml, which failed but still left
cruft in the solr home (e.g. foo_shard1_replica1). Next, I fixed the config
problem and re-created collection "foo", which worked. I still don't think a
create should leave around cruft if it fails but it seems that is now benign
cruft.
> Failed CREATE leaves behind on-disk cruft that DELETE does not remove
> ---------------------------------------------------------------------
>
> Key: SOLR-6639
> URL: https://issues.apache.org/jira/browse/SOLR-6639
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Jessica Cheng Mallet
> Labels: collection-api, solrcloud
>
> When a CREATE api call fails (due to bad config etc.), it leaves behind
> on-disk core directories that a DELETE api call does not delete, which
> results in future CREATE call of with the same collection name to fail. The
> only way to get around this is to go on to the host and manually remove the
> orphaned directories.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
