Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 782D1EC4D for ; Wed, 30 Jan 2013 08:25:15 +0000 (UTC) Received: (qmail 54766 invoked by uid 500); 30 Jan 2013 08:25:14 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 54487 invoked by uid 500); 30 Jan 2013 08:25:13 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 54445 invoked by uid 99); 30 Jan 2013 08:25:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2013 08:25:12 +0000 Date: Wed, 30 Jan 2013 08:25:12 +0000 (UTC) From: =?utf-8?Q?Andr=C3=A9_Bois-Crettez_=28JIRA=29?= To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-3866) CoreAdmin SWAP and RENAME need fixed/defined when using SolrCloud MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-3866?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13566= 284#comment-13566284 ]=20 Andr=C3=A9 Bois-Crettez commented on SOLR-3866: ------------------------------------------ I have the impression that when a CoreAdmin rename occurs, it is somehow co= mmunicated 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 e= ffect on the actual shard being addressed ? That means manually sending a r= ename for each shard to properly swap a distributed collection, but it may = be cleaner this way ? =20 > 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 CoreAdminHandle= r's SWAP and RENAME commands is if you are running in SolrCloud mode. > At the moment, it seems to introduce a disconnect between which "collecti= on" the SolrCore thinks it's a part of (and what appears in the persisted s= olr.xml) vs what collection ZooKeeper thinks the SolrCore(s) that were swap= ed/renamed are a part of. We should either "fix" this, or document it if i= t 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/%3= CCALB4QrP2GZAwLeAiy%3DfcmOLYbc5r0i9Tp1DquyPS8mMJPwCgnw%40mail.gmail.com%3E -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs 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