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 5B61F100DA for ; Thu, 19 Sep 2013 22:21:57 +0000 (UTC) Received: (qmail 49610 invoked by uid 500); 19 Sep 2013 22:21:54 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 49586 invoked by uid 500); 19 Sep 2013 22:21:54 -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 49570 invoked by uid 99); 19 Sep 2013 22:21:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Sep 2013 22:21:53 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jeremiah.jordan@gmail.com designates 209.85.212.53 as permitted sender) Received: from [209.85.212.53] (HELO mail-vb0-f53.google.com) (209.85.212.53) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Sep 2013 22:21:48 +0000 Received: by mail-vb0-f53.google.com with SMTP id i3so6851351vbh.40 for ; Thu, 19 Sep 2013 15:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kBmdEqRljgcgzoW7kP3+j4J/0rdsIq3t+IFGQ2DT9Qc=; b=0MYcnMStxrve8aBpbogAP1K8RrOA+8c6dhHOfhpgffvH62StcSqSmteSbr2J94kz55 RvWzPyg0PBVZAIZiSN70X6i+3vmSYNW3qfpeaSqJ2nFQ1wjHXDj3lCKK9Torz7YHUFli MLyNxeJuDXXZ4CjILOiqrsbvHw3myAbNio4XUr94T37CLeu972k7ZCr7L8PE2ICKJcnp t4YBPY2JsO1oC+hLEquXjjLGyLJGETlP8Lmem4grW4F+6I9fH9hVadQM3H6tVZFuRFh/ p106fJqc/JPMM+iA5461U2DsQ8jEwr48YLSLVB09XGW/IWx45Eg45pqaLfC3wZl9g7G1 kSMA== X-Received: by 10.58.235.193 with SMTP id uo1mr3062815vec.6.1379629288143; Thu, 19 Sep 2013 15:21:28 -0700 (PDT) Received: from [192.168.2.10] (c-71-201-190-179.hsd1.il.comcast.net. [71.201.190.179]) by mx.google.com with ESMTPSA id wp1sm4393790vdb.1.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Sep 2013 15:21:27 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: I don't understand shuffle progress From: Jeremiah D Jordan In-Reply-To: <5239BBAD.10907@gmail.com> Date: Thu, 19 Sep 2013 17:21:36 -0500 Cc: Juan Manuel Formoso , Paulo Motta Content-Transfer-Encoding: quoted-printable Message-Id: <89F93C79-0A2A-48C2-AC38-4ADE2A8EBE50@gmail.com> References: <5239A37F.1030406@gmail.com> <5239BBAD.10907@gmail.com> To: user@cassandra.apache.org X-Mailer: Apple Mail (2.1510) X-Virus-Checked: Checked by ClamAV on apache.org h= ttp://www.datastax.com/documentation/cassandra/1.2/webhelp/index.html#cass= andra/configuration/configVnodesProduction_t.html On Sep 18, 2013, at 9:41 AM, Chris Burroughs = wrote: > = http://www.datastax.com/documentation/cassandra/1.2/webhelp/index.html#cas= sandra/operations/ops_add_dc_to_cluster_t.html >=20 > This is a basic outline. >=20 >=20 > On 09/18/2013 10:32 AM, Juan Manuel Formoso wrote: >> I really like this idea. I can create a new cluster and have it = replicate >> the old one, after it finishes I can remove the original. >>=20 >> Any good resource that explains how to add a new datacenter to a live >> single dc cluster that anybody can recommend? >>=20 >>=20 >> On Wed, Sep 18, 2013 at 9:58 AM, Chris Burroughs >> wrote: >>=20 >>> On 09/17/2013 09:41 PM, Paulo Motta wrote: >>>=20 >>>> So you're saying the only feasible way of enabling VNodes on an = upgraded >>>> C* >>>> 1.2 is by doing fork writes to a brand new cluster + bulk load of = sstables >>>> from the old cluster? Or is it possible to succeed on shuffling, = even if >>>> that means waiting some weeks for the shuffle to complete? >>>>=20 >>>=20 >>> In a multi "DC" cluster situation you *should* be able to bring up a = new >>> DC with vnodes, bootstrap it, and then decommission the old cluster. >>>=20 >>=20 >>=20 >>=20 >=20