You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Per Steffensen (JIRA)" <ji...@apache.org> on 2012/06/21 13:39:42 UTC
[jira] [Created] (SOLR-3563) Collection in ZK not deleted when all
shards has been unloaded
Per Steffensen created SOLR-3563:
------------------------------------
Summary: Collection in ZK not deleted when all shards has been unloaded
Key: SOLR-3563
URL: https://issues.apache.org/jira/browse/SOLR-3563
Project: Solr
Issue Type: Bug
Components: multicore, SolrCloud
Affects Versions: 4.0
Environment: Same as SOLR-3561
Reporter: Per Steffensen
Priority: Minor
Same scanario as SOLR-3561 - deleting shards/cores using CoreAdmin/UNLOAD command.
I have noticed that when I have done CoreAdmin/UNLOAD for all shard under a collection, that the collection and all its slices are still present in ZK under /collections. I might be ok since the operation is called UNLOAD, but I basically want to delete an entire collection and all data related to it (including information about it in ZK).
A delete-collection operation, that also deletes info about the collection under /collections in ZK, would be very nice! Or a delete-shard/core operation and then some nice logic that detects when all shards belonging to a collection has been deleted, and when that has happened deletes info about the collection under /collections in ZK.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Updated] (SOLR-3563) Collection in ZK not deleted when all
shards has been unloaded
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3563:
------------------------------
Fix Version/s: 4.0
> Collection in ZK not deleted when all shards has been unloaded
> --------------------------------------------------------------
>
> Key: SOLR-3563
> URL: https://issues.apache.org/jira/browse/SOLR-3563
> Project: Solr
> Issue Type: Bug
> Components: multicore, SolrCloud
> Affects Versions: 4.0
> Environment: Same as SOLR-3561
> Reporter: Per Steffensen
> Priority: Minor
> Fix For: 4.0
>
>
> Same scanario as SOLR-3561 - deleting shards/cores using CoreAdmin/UNLOAD command.
> I have noticed that when I have done CoreAdmin/UNLOAD for all shard under a collection, that the collection and all its slices are still present in ZK under /collections. I might be ok since the operation is called UNLOAD, but I basically want to delete an entire collection and all data related to it (including information about it in ZK).
> A delete-collection operation, that also deletes info about the collection under /collections in ZK, would be very nice! Or a delete-shard/core operation and then some nice logic that detects when all shards belonging to a collection has been deleted, and when that has happened deletes info about the collection under /collections in ZK.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Assigned] (SOLR-3563) Collection in ZK not deleted when all
shards has been unloaded
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller reassigned SOLR-3563:
---------------------------------
Assignee: Mark Miller
> Collection in ZK not deleted when all shards has been unloaded
> --------------------------------------------------------------
>
> Key: SOLR-3563
> URL: https://issues.apache.org/jira/browse/SOLR-3563
> Project: Solr
> Issue Type: Bug
> Components: multicore, SolrCloud
> Affects Versions: 4.0
> Environment: Same as SOLR-3561
> Reporter: Per Steffensen
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.0
>
>
> Same scanario as SOLR-3561 - deleting shards/cores using CoreAdmin/UNLOAD command.
> I have noticed that when I have done CoreAdmin/UNLOAD for all shard under a collection, that the collection and all its slices are still present in ZK under /collections. I might be ok since the operation is called UNLOAD, but I basically want to delete an entire collection and all data related to it (including information about it in ZK).
> A delete-collection operation, that also deletes info about the collection under /collections in ZK, would be very nice! Or a delete-shard/core operation and then some nice logic that detects when all shards belonging to a collection has been deleted, and when that has happened deletes info about the collection under /collections in ZK.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (SOLR-3563) Collection in ZK not deleted when
all shards has been unloaded
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399507#comment-13399507 ]
Mark Miller commented on SOLR-3563:
-----------------------------------
I've add this to the work I did on the collections API - it's needed there for collection removal. Should be committing a first iteration of that soon.
> Collection in ZK not deleted when all shards has been unloaded
> --------------------------------------------------------------
>
> Key: SOLR-3563
> URL: https://issues.apache.org/jira/browse/SOLR-3563
> Project: Solr
> Issue Type: Bug
> Components: multicore, SolrCloud
> Affects Versions: 4.0
> Environment: Same as SOLR-3561
> Reporter: Per Steffensen
> Priority: Minor
> Fix For: 4.0
>
>
> Same scanario as SOLR-3561 - deleting shards/cores using CoreAdmin/UNLOAD command.
> I have noticed that when I have done CoreAdmin/UNLOAD for all shard under a collection, that the collection and all its slices are still present in ZK under /collections. I might be ok since the operation is called UNLOAD, but I basically want to delete an entire collection and all data related to it (including information about it in ZK).
> A delete-collection operation, that also deletes info about the collection under /collections in ZK, would be very nice! Or a delete-shard/core operation and then some nice logic that detects when all shards belonging to a collection has been deleted, and when that has happened deletes info about the collection under /collections in ZK.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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