You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "André Bois-Crettez (JIRA)" <ji...@apache.org> on 2013/01/30 09:31:15 UTC
[jira] [Comment Edited] (SOLR-3866) CoreAdmin SWAP and RENAME need
fixed/defined when using SolrCloud
[ https://issues.apache.org/jira/browse/SOLR-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566284#comment-13566284 ]
André Bois-Crettez edited comment on SOLR-3866 at 1/30/13 8:29 AM:
-------------------------------------------------------------------
I have the impression that when a CoreAdmin rename/swap occurs, it is somehow communicated across the whole cloud and messes up the Zk conf (I have not yet been able to trace exactly what happens).
Wild guess, but what if the CoreAdmin rename/swap is "silent" and only have an effect on the actual shard being addressed ? That means manually sending a rename/swap for each shard to properly change a distributed collection, but it may be cleaner this way ?
was (Author: aboiscrettez):
I have the impression that when a CoreAdmin rename occurs, it is somehow communicated across the whole cloud and messes up the Zk conf (I have not yet been able to trace exactly what happens).
Wild guess, but what if the CoreAdmin rename is "silent" and only have an effect on the actual shard being addressed ? That means manually sending a rename for each shard to properly swap a distributed collection, but it may be cleaner this way ?
> CoreAdmin SWAP and RENAME need fixed/defined when using SolrCloud
> -----------------------------------------------------------------
>
> Key: SOLR-3866
> URL: https://issues.apache.org/jira/browse/SOLR-3866
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0
> Reporter: Hoss Man
>
> We need to define what the expected behavior of using the CoreAdminHandler's SWAP and RENAME commands is if you are running in SolrCloud mode.
> At the moment, it seems to introduce a disconnect between which "collection" the SolrCore thinks it's a part of (and what appears in the persisted solr.xml) vs what collection ZooKeeper thinks the SolrCore(s) that were swaped/renamed are a part of. We should either "fix" this, or document it if it as actually consistent and intentional for low level controls, or disable commands like SWAP/RENAME in SolrCloud mode
> https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201209.mbox/%3CCALB4QrP2GZAwLeAiy%3DfcmOLYbc5r0i9Tp1DquyPS8mMJPwCgnw%40mail.gmail.com%3E
--
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