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 910268CE4 for ; Mon, 5 Sep 2011 19:57:29 +0000 (UTC) Received: (qmail 55497 invoked by uid 500); 5 Sep 2011 19:57:27 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55442 invoked by uid 500); 5 Sep 2011 19:57:27 -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 55434 invoked by uid 99); 5 Sep 2011 19:57:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2011 19:57:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of talk2amulya@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2011 19:57:20 +0000 Received: by vws12 with SMTP id 12so5097262vws.31 for ; Mon, 05 Sep 2011 12:56:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=r05mgL2P3Fb7Sjg7wJ8d4zyXuTsnuzMTc025/yshd70=; b=Y9LMziCku6mrUbsr1yK9ggkWe/tJOUquBmM8HuBh0dmCmqqzSH88U4F9qWX2i7N363 rU8xkUc3LBQwAAOcPsxfjPvyq6aOOPP2HdOivaZcNQlMsTKotCBkKJoelUgVsL5pmdUf q3hXI9BsRyNCUqFSSoHMAtS3R6stxBH6YKqK0= MIME-Version: 1.0 Received: by 10.52.174.199 with SMTP id bu7mr3995787vdc.295.1315252619567; Mon, 05 Sep 2011 12:56:59 -0700 (PDT) Received: by 10.52.187.4 with HTTP; Mon, 5 Sep 2011 12:56:59 -0700 (PDT) In-Reply-To: References: Date: Mon, 5 Sep 2011 15:56:59 -0400 Message-ID: Subject: Re: load balance issue From: amulya rattan To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec51d2f302de1a704ac371d95 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec51d2f302de1a704ac371d95 Content-Type: text/plain; charset=ISO-8859-1 Ah, missed that. Thanks for the pointer. While we are at it, the doc says that if I am doubling the strength of my cluster, and I assign calculated tokens to the new nodes, i don't need to do the nodetool move for old nodes. Won't I have to assign the old nodes with their new respective tokens too? If I had 4 nodes and I add 4 more, the token distribution for each node changes. Then how could I get away with not assigning old nodes with new tokens? ~Amulya On Mon, Sep 5, 2011 at 4:12 AM, Sylvain Lebresne wrote: > Have you done step 6 of the 'To add nodes to a Cassandra cluster' of > http://www.datastax.com/docs/0.8/operations/clustering#adding-capacity, > aka, run nodetool cleanup on the previously existing nodes ? > > -- > Sylvain > > On Sun, Sep 4, 2011 at 11:58 AM, amulya rattan > wrote: > > Hi there, > > I had a 3 nodes ring, added a 4th one, and moved others to appropriate > > tokens..doing nodetool ring shows: > > 127.0.0.1 datacenter1 rack1 Up Normal 348.82 MB > > 25.00% 0 > > 127.0.0.2 datacenter1 rack1 Up Normal 349.81 MB > > 25.00% 42535295865117307932921825928971026432 > > 127.0.0.3 datacenter1 rack1 Up Normal 437.04 MB > > 25.00% 85070591730234615865843651857942052864 > > 127.0.0.4 datacenter1 rack1 Up Normal 261.74 MB > > 25.00% 127605887595351923798765477786913079296 > > Although it shows 25% on all nodes, the data distribution seems totally > > unbalanced, how did that happen? > > Also if I happen to have a thousand node cluster, and add another 100 > nodes, > > is it ok to start moving all nodes to their respective new tokens > > simultaneously or one-by-one? > > Any response is appreciated. > > ~Amulya > --bcaec51d2f302de1a704ac371d95 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ah, missed that. Thanks for the pointer.=A0
While we are at it, the doc= says that if I am doubling the strength of my cluster, and I assign calcul= ated tokens to the new nodes, i don't need to do the nodetool move for = old nodes. Won't I have to assign the old nodes with their new respecti= ve tokens too? If I had 4 nodes and I add 4 more, the token distribution fo= r each node changes. Then how could I get away with not assigning old nodes= with new tokens?

~Amulya=A0

On Mon, Se= p 5, 2011 at 4:12 AM, Sylvain Lebresne <sylvain@datastax.com> wrote:
Have you done step 6 of the 'To add nodes to a Cassandra cluster' o= f
http://www.datastax.com/docs/0.8/operations/clust= ering#adding-capacity,
aka, run nodetool cleanup on the previously existing nodes ?

--
Sylvain

On Sun, Sep 4, 2011 at 11:58 AM, amulya rattan <talk2amulya@gmail.com> wrote:
> Hi there,
> I had a 3 nodes ring, added a 4th one, =A0and moved others to appropri= ate
> tokens..doing nodetool ring shows:
> 127.0.0.1 =A0 =A0 =A0 datacenter1 rack1 =A0 =A0 =A0 Up =A0 =A0 Normal = =A0348.82 MB
> 25.00% =A00
> 127.0.0.2 =A0 =A0 =A0 datacenter1 rack1 =A0 =A0 =A0 Up =A0 =A0 Normal = =A0349.81 MB
> 25.00% =A042535295865117307932921825928971026432
> 127.0.0.3 =A0 =A0 =A0 datacenter1 rack1 =A0 =A0 =A0 Up =A0 =A0 Normal = =A0437.04 MB
> 25.00%=A0=A085070591730234615865843651857942052864
> 127.0.0.4 =A0 =A0 =A0 datacenter1 rack1 =A0 =A0 =A0 Up =A0 =A0 Normal = =A0261.74 MB
> 25.00%=A0=A0127605887595351923798765477786913079296
> Although it shows 25% on all nodes, the data distribution seems totall= y
> unbalanced, how did that happen?
> Also if I happen to have a thousand node cluster, and add another 100 = nodes,
> is it ok to start moving all nodes to their respective new tokens
> simultaneously or one-by-one?
> Any response is appreciated.
> ~Amulya

--bcaec51d2f302de1a704ac371d95--