Return-Path: 
 <user-return-19941-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A11BD7B87
	for <apmail-cassandra-user-archive@www.apache.org>;
 Wed, 17 Aug 2011 20:46:30 +0000 (UTC)
Received: (qmail 98414 invoked by uid 500); 17 Aug 2011 20:46:28 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 98328 invoked by uid 500); 17 Aug 2011 20:46:28 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 98320 invoked by uid 99); 17 Aug 2011 20:46:27 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2011 20:46:27 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of watcherfr@gmail.com designates
 209.85.210.48 as permitted sender)
Received: from [209.85.210.48] (HELO mail-pz0-f48.google.com) (209.85.210.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2011 20:46:20 +0000
Received: by pzk34 with SMTP id 34so1571888pzk.21
        for <user@cassandra.apache.org>; Wed, 17 Aug 2011 13:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=Rs6zBPj0OPcz7DqT5OgyeKvww1/+/1UJi5aI/Dc4v3M=;
        b=QBnHR2CKQkVaep++d9id4CvuGnytOC/nXU2oACcaEdom5yS5ZPRAIda9UbKJuwsMFZ
         3qnWt8FdHQM6+lSU7/SFfeYeJZA4u8OZlJFxbdaSfucrbjcy8oUjvTuQbhslOENKW/+6
         1TnccXOE+yJmieMkQAK4A5qWmclQJSj9gQsHk=
MIME-Version: 1.0
Received: by 10.142.52.17 with SMTP id z17mr669093wfz.143.1313613958913; Wed,
 17 Aug 2011 13:45:58 -0700 (PDT)
Received: by 10.142.203.21 with HTTP; Wed, 17 Aug 2011 13:45:58 -0700 (PDT)
Date: Wed, 17 Aug 2011 22:45:58 +0200
Message-ID: 
 <CAHwsXYk3MhYnPyLNYXM_+zGwzrpVYSGnk_3ji98aQWt5YsKn4w@mail.gmail.com>
Subject: Repairs are both ways ?
From: Philippe <watcherfr@gmail.com>
To: user <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=000e0cd242e6649f0904aab99531
X-Virus-Checked: Checked by ClamAV on apache.org

--000e0cd242e6649f0904aab99531
Content-Type: text/plain; charset=ISO-8859-1

Looking at the logs, I see that repairs stream data TO and FROM a node to
its replicas.
So on a 3-node RF=3 cluster, one only needs to launch repairs on a single
node right ?

Thanks

--000e0cd242e6649f0904aab99531
Content-Type: text/html; charset=ISO-8859-1

Looking at the logs, I see that repairs stream data TO and FROM a node to its replicas.<div>So on a 3-node RF=3 cluster, one only needs to launch repairs on a single node right ?</div><div><br></div><div>Thanks</div>

--000e0cd242e6649f0904aab99531--