Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 94271 invoked from network); 15 Jul 2010 18:55:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Jul 2010 18:55:26 -0000 Received: (qmail 80068 invoked by uid 500); 15 Jul 2010 18:55:25 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 80026 invoked by uid 500); 15 Jul 2010 18:55:24 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 80017 invoked by uid 99); 15 Jul 2010 18:55:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jul 2010 18:55:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bburruss@real.com designates 207.188.23.4 as permitted sender) Received: from [207.188.23.4] (HELO kal-el.real.com) (207.188.23.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jul 2010 18:55:15 +0000 Received: from seacas01.corp.real.com ([::ffff:192.168.139.56]) (TLS: TLSv1/SSLv3,128bits,AES128-SHA) by kal-el.real.com with esmtp; Thu, 15 Jul 2010 11:54:53 -0700 id 00080053.4C3F597D.00001019 Received: from [192.168.129.75] (192.168.198.6) by seacas01.corp.real.com (192.168.139.56) with Microsoft SMTP Server id 8.2.254.0; Thu, 15 Jul 2010 11:54:50 -0700 Subject: nodetool repair From: "B. Todd Burruss" To: user@cassandra.apache.org Content-Type: text/plain; charset="UTF-8" Date: Thu, 15 Jul 2010 11:54:53 -0700 Message-ID: <1279220093.3118.10.camel@btoddb-ubuntu> MIME-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Old-Return-Path: bburruss@real.com X-Virus-Checked: Checked by ClamAV on apache.org if i have N=3 and run nodetool repair on node X. i assume that merkle trees (at a minimum) are calculated on nodes X, X+1, and X+2 (since N=3). when the repair is finished are nodes X, X+1, and X+2 all in sync with respect to node X's data? or does X have the latest data and X+1 and X+2 still in need of repair? since merkle trees are calculated for all replicas, seems like a good time to sync all of them. i understand that X+1 and X+2 are replicas for nodes other than X and may still need repairing. thx