Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6EF361075C for ; Thu, 28 Nov 2013 16:07:24 +0000 (UTC) Received: (qmail 34943 invoked by uid 500); 28 Nov 2013 16:05:06 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 34868 invoked by uid 500); 28 Nov 2013 16:04:46 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 34785 invoked by uid 99); 28 Nov 2013 16:04:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Nov 2013 16:04:36 +0000 Date: Thu, 28 Nov 2013 16:04:36 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-6218) Reduce WAN traffic while doing repairs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6218: -------------------------------------- Reviewer: Lyuben Todorov Component/s: Tools Fix Version/s: 2.0.4 Issue Type: New Feature (was: Improvement) > Reduce WAN traffic while doing repairs > -------------------------------------- > > Key: CASSANDRA-6218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6218 > Project: Cassandra > Issue Type: New Feature > Components: Core, Tools > Reporter: sankalp kohli > Priority: Minor > Fix For: 2.0.4 > > Attachments: trunk-6218.txt > > > The way we send out data that does not match over WAN can be improved. > Example: Say there are four nodes(A,B,C,D) which are replica of a range we are repairing. A, B is in DC1 and C,D is in DC2. If A does not have the data which other replicas have, then we will have following streams > 1) A to B and back > 2) A to C and back(Goes over WAN) > 3) A to D and back(Goes over WAN) > One of the ways of doing it to reduce WAN traffic is this. > 1) Repair A and B only with each other and C and D with each other starting at same time t. > 2) Once these repairs have finished, A,B and C,D are in sync with respect to time t. > 3) Now run a repair between A and C, the streams which are exchanged as a result of the diff will also be streamed to B and D via A and C(C and D behaves like a proxy to the streams). > For a replication of DC1:2,DC2:2, the WAN traffic will get reduced by 50% and even more for higher replication factors. > -- This message was sent by Atlassian JIRA (v6.1#6144)