[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603437#comment-15603437
]
Jeremy Hanna commented on CASSANDRA-12816:
------------------------------------------
If you change it to NetworkTopologyStrategy, the strategy is datacenter aware.
You are then able to specify the datacenter where the replicas will be stored.
If you aren't using SimpleStrategy and you bootstrap other nodes in another
datacenter, then try to rebuild, it will likely try to put data for those
keyspaces in the new datacenter. The rebuild operation requires a source
datacenter argument, so I wonder if it's failing because the source datacenter
in this case doesn't have all of the data according to the replication
strategies for those keyspaces. So I would always change to NTS before trying
rebuild.
> 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)
