Mike Drob created SOLR-7187:
-------------------------------
Summary: SolrCloud does not fully clean collection after delete
Key: SOLR-7187
URL: https://issues.apache.org/jira/browse/SOLR-7187
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 4.10.3
Reporter: Mike Drob
When I attempt to delete a collection using
{{/admin/collections?action=DELETE&name=collection1}} if I go into HDFS I will
still see remnants from the collection. No files, but empty directories stick
around.
{noformat}
[root@drob-search-cdh-25682 ~]# sudo -u hdfs hdfs dfs -ls -R /solr/collection1
drwxr-xr-x - solr solr 0 2015-03-03 15:42
/solr/collection1/core_node1
drwxr-xr-x - solr solr 0 2015-03-03 15:42
/solr/collection1/core_node2
drwxr-xr-x - solr solr 0 2015-03-03 15:42
/solr/collection1/core_node3
drwxr-xr-x - solr solr 0 2015-03-03 15:42
/solr/collection1/core_node4
drwxr-xr-x - solr solr 0 2015-03-03 15:42
/solr/collection1/core_node5
drwxr-xr-x - solr solr 0 2015-03-03 15:42
/solr/collection1/core_node6
{noformat}
In the logs, after deleting all the data, I see:
{noformat}
2015-03-03 15:42:44,453 INFO org.apache.solr.handler.admin.CollectionsHandler:
Deleting Collection : name=collection1&action=DELETE
2015-03-03 15:42:44,465 INFO org.apache.solr.cloud.DistributedQueue:
LatchChildWatcher fired on path: /overseer/collection-queue-work state:
SyncConnected type NodeChildrenChanged
2015-03-03 15:42:44,474 INFO org.apache.solr.cloud.OverseerCollectionProcessor:
Overseer Collection Processor: Get the message
id:/overseer/collection-queue-work/qn-0000000012 message:{
"operation":"deletecollection",
"name":"collection1"}
2015-03-03 15:42:44,474 WARN org.apache.solr.cloud.OverseerCollectionProcessor:
OverseerCollectionProcessor.processMessage : deletecollection , {
"operation":"deletecollection",
"name":"collection1"}
2015-03-03 15:42:44,474 INFO org.apache.solr.cloud.OverseerCollectionProcessor:
Executing Collection Cmd :
action=UNLOAD&deleteInstanceDir=true&deleteDataDir=true
2015-03-03 15:42:44,475 ERROR
org.apache.solr.cloud.OverseerCollectionProcessor: Collection deletecollection
of deletecollection failed:org.apache.solr.common.SolrException: Could not find
collection:collection1
at
org.apache.solr.common.cloud.ClusterState.getCollection(ClusterState.java:145)
at
org.apache.solr.cloud.OverseerCollectionProcessor.collectionCmd(OverseerCollectionProcessor.java:1074)
at
org.apache.solr.cloud.OverseerCollectionProcessor.deleteCollection(OverseerCollectionProcessor.java:296)
at
org.apache.solr.cloud.OverseerCollectionProcessor.processMessage(OverseerCollectionProcessor.java:244)
at
org.apache.solr.cloud.OverseerCollectionProcessor.run(OverseerCollectionProcessor.java:171)
at java.lang.Thread.run(Thread.java:745)
2015-03-03 15:42:44,498 INFO org.apache.solr.cloud.DistributedQueue:
LatchChildWatcher fired on path: /overseer/collection-queue-work/qnr-0000000012
state: SyncConnected type NodeDataChanged
2015-03-03 15:42:44,506 INFO org.apache.solr.cloud.DistributedQueue:
LatchChildWatcher fired on path: /overseer/collection-queue-work state:
SyncConnected type NodeChildrenChanged
2015-03-03 15:42:44,506 INFO org.apache.solr.cloud.OverseerCollectionProcessor:
Overseer Collection Processor: Message
id:/overseer/collection-queue-work/qn-0000000012 complete, response:{Operation
deletecollection caused exception:=org.apache.solr.common.SolrException: Could
not find collection:collection1,exception={msg=Could not find
collection:collection1,rspCode=400}}
{noformat}
This might be related to SOLR-5023, but I'm not sure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
