Return-Path: 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 492A5106BB for ; Tue, 9 Jul 2013 17:31:46 +0000 (UTC) Received: (qmail 61895 invoked by uid 500); 9 Jul 2013 17:31:43 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 61872 invoked by uid 500); 9 Jul 2013 17:31:43 -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 61864 invoked by uid 99); 9 Jul 2013 17:31:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 17:31:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rcoli@eventbrite.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 17:31:39 +0000 Received: by mail-qc0-f182.google.com with SMTP id e10so3172905qcy.27 for ; Tue, 09 Jul 2013 10:31:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=dnWLs8A1d217vY6/zmD3QfONjolQ8jUt3URZYxTeUow=; b=fd098KLGxhT293Wh5bi6cOWjTnM+7qPPNkn0FxkD4rHRRKl4l0PAutM5BCle9AgmBN EdUalbfLRMUbDyerDuKFtJNax6O59VC6d2W1m7PWYsSJQPjtWKaBfSDxkBxyz68P6fZJ Ou/rvef5Z2uffH0c8MwiOxIus6zETjxRs76mUe3CQTKO/vOhycT5t0AqkQYhRW+kvUrc rrXp31+ofi2tTwaj7W+xOushYenmz55KmyVx117MTwrL5tJN3BbbKcrFs8D8K0Cao/h4 2KQwtUq/SUhfTqLGn6Bjm4gMS0F5txnxkvTmFofkIjlqY7ZEORGgewFJvQA9f/ZxQH12 9PzQ== MIME-Version: 1.0 X-Received: by 10.49.14.101 with SMTP id o5mr21945577qec.55.1373391078422; Tue, 09 Jul 2013 10:31:18 -0700 (PDT) Received: by 10.49.129.131 with HTTP; Tue, 9 Jul 2013 10:31:18 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Jul 2013 10:31:18 -0700 Message-ID: Subject: Re: Migrating data from 2 node cluster to a 3 node cluster From: Robert Coli To: "user@cassandra.apache.org" Cc: Ananth Gundabattula Content-Type: multipart/alternative; boundary=047d7b676b3c5e139e04e11787d3 X-Gm-Message-State: ALoCoQnN3BhXVyxuu7xntm47VEYqHUEmIlRPmogSQi9OaAFkF+sOltzYe3uXwgkEf+gI6eQM+Unl X-Virus-Checked: Checked by ClamAV on apache.org --047d7b676b3c5e139e04e11787d3 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jul 9, 2013 at 12:36 AM, Ananth Gundabattula < agundabattula@threatmetrix.com> wrote: > > The thread below makes me wonder "Does RF matter when using sstable loader.?" My assumption was that stable loader will take care of RF when the streaming is done but just wanted to cross check. We are currently moving data from a RF=1 to RF=3 cluster by using sstable loader tool. We will of course be running repair on the destination nodes but was wondering how is the following issue resolved using a repair if my understanding is wrong? sstableloader does in fact stream to all endpoints. That's why it's valuable that it has an --ignores option : if you successfully streamed to 2/3 replicas and 1/3 failed, you can --ignores the 2 which completed. =Rob --047d7b676b3c5e139e04e11787d3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Jul 9, 2013 at 12:36 AM, Ananth Gundabattula <<= a href=3D"mailto:agundabattula@threatmetrix.com">agundabattula@threatmetrix= .com> wrote:
>
> The thread below makes me wonder "= Does RF matter when using sstable loader.?" =A0My assumption was that = stable loader will take care of RF when the streaming is done but just want= ed to cross check. We are currently moving data from a RF=3D1 to RF=3D3 clu= ster by using sstable loader tool. We will of course be running repair on t= he destination nodes but was wondering how is the following issue resolved = using a repair if my understanding is wrong?

sstableloader does in fact stream to all endpoints. That's why it&#= 39;s valuable that it has an --ignores option : if you successfully streame= d to 2/3 replicas and 1/3 failed, you can --ignores the 2 which completed.<= br>

=3DRob


--047d7b676b3c5e139e04e11787d3--