[ 
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jai Bheemsen Rao Dhanwada reopened CASSANDRA-12816:
---------------------------------------------------
    Reproduced In: 2.1.x
    Since Version: 2.1.16

[~jjordan] I have encountered this issue again and now it is complaining about 
the non-system keyspace.
{code:java}
[jaibheemsen@node01 ~]$ nodetool rebuild us-east
nodetool: Unable to find sufficient sources for streaming range 
(1773952483933901933,1774688434180951054] in keyspace user_prod
See 'nodetool help' or 'nodetool help <command>'.
[jaibheemsen@node01 ~]$
{code}

C* version : 2.1.16
user_prod: keyspace is present in us-west-2 but not in us-east. I am doing a 
nodetool rebuild in us-west-2 to stream some data from the us-east

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

Reply via email to