[
https://issues.apache.org/jira/browse/SOLR-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496352#comment-13496352
]
Ryan Josal commented on SOLR-3866:
----------------------------------
The use case I (and it appears the author of the instigating thread for this
issue: http://osdir.com/ml/solr-user.lucene.apache.org/2012-09/msg00893.html)
have for CoreAdmin SWAP is to support a backup core (on deck core) that I can
rebuild the index from scratch on.
> 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: [email protected]
For additional commands, e-mail: [email protected]
