You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alexandre Rafalovitch (JIRA)" <ji...@apache.org> on 2016/10/02 07:05:20 UTC
[jira] [Closed] (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:all-tabpanel ]
Alexandre Rafalovitch closed SOLR-3866.
---------------------------------------
Resolution: Implemented
Was marked for closure a year ago. No objections were raised.
> 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
> Assignee: Erick Erickson
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org