lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Bois-Crettez (JIRA) <>
Subject [jira] [Commented] (SOLR-3866) CoreAdmin SWAP and RENAME need fixed/defined when using SolrCloud
Date Wed, 30 Jan 2013 08:25:12 GMT


André Bois-Crettez commented on SOLR-3866:

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

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:
>             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

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message