Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 62728 invoked from network); 13 Aug 2010 16:52:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Aug 2010 16:52:32 -0000 Received: (qmail 91577 invoked by uid 500); 13 Aug 2010 16:52:31 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 91502 invoked by uid 500); 13 Aug 2010 16:52:30 -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 91494 invoked by uid 99); 13 Aug 2010 16:52:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 16:52:30 +0000 X-ASF-Spam-Status: No, hits=4.3 required=10.0 tests=FS_REPLICA,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 16:52:23 +0000 Received: by wwj40 with SMTP id 40so3648475wwj.25 for ; Fri, 13 Aug 2010 09:51:58 -0700 (PDT) Received: by 10.216.159.195 with SMTP id s45mr1522522wek.43.1281718318301; Fri, 13 Aug 2010 09:51:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.234.219 with HTTP; Fri, 13 Aug 2010 09:51:38 -0700 (PDT) In-Reply-To: References: From: Benjamin Black Date: Fri, 13 Aug 2010 09:51:38 -0700 Message-ID: Subject: Re: Data Distribution / Replication To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Aug 13, 2010 at 9:48 AM, Oleg Anastasjev wrote= : > Benjamin Black b3k.us> writes: > >> > 3. I waited for the data to replicate, which didn't happen. >> >> Correct, you need to run nodetool repair because the nodes were not >> present when the writes came in. =A0You can also use a higher >> consistency level to force read repair before returning data, which >> will incrementally repair things. >> > > Alternatively you could configure new nodes to bootstrap in storage-conf.= xml. If > bootstrap is enalbed you'll get data replicated on them as soon as they j= oin > cluster. > My recommendation is to leave Autobootstrap disabled, copy the datafiles over, and then run cleanup. It is faster and more reliable than streaming, in my experience. b