Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 19439 invoked from network); 12 Feb 2010 00:42:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Feb 2010 00:42:14 -0000 Received: (qmail 95971 invoked by uid 500); 12 Feb 2010 00:42:14 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 95950 invoked by uid 500); 12 Feb 2010 00:42:14 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 95940 invoked by uid 99); 12 Feb 2010 00:42:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Feb 2010 00:42:14 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of weijunli@gmail.com designates 209.85.216.186 as permitted sender) Received: from [209.85.216.186] (HELO mail-px0-f186.google.com) (209.85.216.186) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Feb 2010 00:42:06 +0000 Received: by pxi16 with SMTP id 16so1204400pxi.29 for ; Thu, 11 Feb 2010 16:41:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=8MUIeV5momLvt0st0xX9g2ylBHKwcxF0gy3rMY9VPbU=; b=eIHZHrVo4RaobO2xxIqD/ugV7ouGpVSSCDJ9MBgT0e2z1UFJOFVYPAvZdcVfiT7ODA d0GyC4aQnOCecxgc28uWz06JT9sEuh9VSPmxteZ9pDn3wlLONyH8bdgu+zppJCCcyGKC h3wsEyGJTJj9Q9SZ1SszSPHYxHzwJ+50+Xed8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=c9dMZ/E1yhww4Sxpy/JeN92yR9nXxetnsb4lqItD/dQfBp3zof+eC6vdf7WtTdkTwJ ugS1yuLaImM6K24+xgtbVHmpuTKKttzuSdqOjCxbtW7PWSEk0V2s3fkzDtwLUum9gpYD AECyNuX9Gzr+5PmNhI4QbZbanBf1Qkas4algI= MIME-Version: 1.0 Received: by 10.115.99.29 with SMTP id b29mr419580wam.131.1265935304590; Thu, 11 Feb 2010 16:41:44 -0800 (PST) Date: Thu, 11 Feb 2010 16:41:44 -0800 Message-ID: Subject: Rebalance after adding new nodes From: Weijun Li To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e64dbc0e2384e5047f5c88f4 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64dbc0e2384e5047f5c88f4 Content-Type: text/plain; charset=ISO-8859-1 When you add a new node, cassandra will pick the node that has the most data then split its token. In this case the data distribution among all nodes become uneven. What's the right strategy/steps to rebalance the node load after adding new nodes? Here's one example: I have a cluster of node A, B, C, D. Now I want to add E and F, after adding the nodes, the data distribution will change from 1/1/1/1 to 1/1/0.5/0.5/0.5/0.5, is this correct? Thanks, -Weijun --0016e64dbc0e2384e5047f5c88f4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable When you add a new node, cassandra will pick the node that has the most dat= a then split its token. In this case the data distribution among all nodes = become uneven. What's the right strategy/steps to rebalance the node lo= ad after adding new nodes? Here's one example: I have a cluster of node= A, B, C, D. Now I want to add E and F, after adding the nodes, the data di= stribution will change from 1/1/1/1 to 1/1/0.5/0.5/0.5/0.5, is this correct= ?

Thanks,
-Weijun
--0016e64dbc0e2384e5047f5c88f4--