Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 26 Jul 2016 17:34:20 +0000 (UTC)
From: "Paulo Motta (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12992589.1469542475000.136625.1469554460546@Atlassian.JIRA>
In-Reply-To: <JIRA.12992589.1469542475000@Atlassian.JIRA>
References: <JIRA.12992589.1469542475000@Atlassian.JIRA> <JIRA.12992589.1469542475191@arcas>
Subject: [jira] [Commented] (CASSANDRA-12296) system_auth can't be rebuilt
 by default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 26 Jul 2016 17:34:22 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-12296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394150#comment-15394150 ] 

Paulo Motta commented on CASSANDRA-12296:
-----------------------------------------

I wonder if this is really a bug, given that we recommend users to switch their keyspaces to use {{NetworkTopologyStrategy}} [before performing a rebuild|https://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html]:

bq.  Ensure that you are using NetworkTopologyStrategy for all of your keyspaces.

But perhaps we can indeed update the message to make this more clear.

> system_auth can't be rebuilt by default
> ---------------------------------------
>
>                 Key: CASSANDRA-12296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12296
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>
> This came up in discussion of CASSANDRA-11687. {{nodetool rebuild}} was failing in a dtest. [~pauloricardomg] explained:
> bq. before [CASSANDRA-11848] the local node could be considered a source, while now sources are restricted only to dc2, so since {{system_auth}} uses {{SimpleStrategy}} depending on the token arrangement there could or not be sources from dc2. Fix is to either use {{-Dcassandra.consistent.rangemovement=false}} or update {{system_auth}} to use {{NetworkTopologyStrategy}} with 2 dcs..
> This is, at the very least, a UX bug. When {{rebuild}} fails, it fails with
> {code}
> nodetool: Unable to find sufficient sources for streaming range (-3287869951390391138,-1624006824486474209] in keyspace system_auth with RF=1.If you want to ignore this, consider using system property -Dcassandra.consistent.rangemovement=false.
> {code}
> which suggests that a user should give up consistency guarantees when it's not necessary.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)