You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Fabien Rousseau (JIRA)" <ji...@apache.org> on 2016/06/18 21:31:05 UTC
[jira] [Issue Comment Deleted] (CASSANDRA-12015) Rebuilding from
another DC should use different sources
[ https://issues.apache.org/jira/browse/CASSANDRA-12015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabien Rousseau updated CASSANDRA-12015:
----------------------------------------
Comment: was deleted
(was: Hum, I first tried adding a method "sortByDcRack" but it still had the same behaviour...
I finally tried another approach (inspired by NetworkTopologyStrategy.calculateNaturalEndpoints method) using the TokenMetadata.ringIterator() which returns the next endpoints after a "startToken".
Note: a basic unit test is attached in the patch )
> Rebuilding from another DC should use different sources
> -------------------------------------------------------
>
> Key: CASSANDRA-12015
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12015
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Fabien Rousseau
>
> Currently, when adding a new DC (ex: DC2) and rebuilding it from an existing DC (ex: DC1), only the closest replica is used as a "source of data".
> It works but is not optimal, because in case of an RF=3 and 3 nodes cluster, only one node in DC1 is streaming the data to DC2.
> To build the new DC in a reasonable time, it would be better, in that case, to stream from multiple sources, thus distributing more evenly the load.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)