cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
Date Mon, 24 Oct 2016 21:27:58 GMT

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

Jeremy Hanna commented on CASSANDRA-12816:
------------------------------------------

If it is using the LocalStrategy, don't change it.  In fact I don't think you can change it.
 If it's not using the local strategy, set it to NetworkTopologyStrategy.

> Rebuild failing while adding new datacenter
> -------------------------------------------
>
>                 Key: CASSANDRA-12816
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jai Bheemsen Rao Dhanwada
>            Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the cluster to another
region/DC. I am seeing the below error while doing a "nodetool rebuild -- name_of_existing_data_center"
.  
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range (-402178150752044282,-396707578307430827]
in keyspace system_distributed
> See 'nodetool help' or 'nodetool help <command>'.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where keyspace_name='system_distributed';
>  keyspace_name | durable_writes | replication
> ---------------+----------------+-------------------------------------------------------------------------------------
>  system_distributed |           True | {'class': 'org.apache.cassandra.locator.SimpleStrategy',
'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't seen this
issue with the older versions?



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

Mime
View raw message