You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/20 22:34:52 UTC

[jira] [Resolved] (CASSANDRA-2609) Repair multi-DC awareness

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

Jonathan Ellis resolved CASSANDRA-2609.
---------------------------------------

    Resolution: Won't Fix
    
> Repair multi-DC awareness
> -------------------------
>
>                 Key: CASSANDRA-2609
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2609
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Priority: Minor
>              Labels: ponies
>
> Repair has no multi-DC awareness in that if you have 2 DC with 3 replica in each, a repair of a node will transit 3 merkle tree cross-DC and potentially initiate as many cross-DC streaming (with likely a non null intersection between those). In theory, we could repair separately in each DC, then repair between only two node cross-DC (that we know are up to date in their respective DC) and finally re-repair in the separate DC (to pass the cross-DC changes to all nodes of the DC).
> It is yet unclear to me if we can make that efficient enough that it is worth the added complexity, so this is really meant as an exploratory ticket. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira