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 676D66536 for ; Thu, 26 May 2011 13:22:21 +0000 (UTC) Received: (qmail 55646 invoked by uid 500); 26 May 2011 13:22:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55602 invoked by uid 500); 26 May 2011 13:22:18 -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 55556 invoked by uid 99); 26 May 2011 13:22:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 13:22:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sdolgy@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vx0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 13:22:13 +0000 Received: by vxg33 with SMTP id 33so642614vxg.31 for ; Thu, 26 May 2011 06:21:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; bh=p2cjBz6VDMOlO5IPzHgvsqAFIsp77KmIE588k/wWfo4=; b=DTi8Wuo9jTeanWS7c3QsHZGsLD7vYt0M+vzYfj01c9aY3OdU28589WsTq4cTUEOBub 2mOa4L+bzXQtyzVTurimWcvrw87QaEeQDMluW2cH92cR5jyTr+aID50qNXs9/FzzYLKs C3qGiCI0YPhEGK3EtMTJzWIlm4OviCaqK7I6o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=pv3LFvNvvVcSDKsp7ybq3T2gxxbwqb5dy58+UzWFZZcQGaxlWFagKERUR2GPITd6YL GZvDwe8m60NYVZdyD0ojsloDyZP/ph1xaFxODqch0Aeqf9VvkSy/PdnNh5P4wgmwH2VL +AW17KoWkgpB5fo18BhSorAt4XsM7JnsRPvwU= Received: by 10.52.68.205 with SMTP id y13mr1143026vdt.76.1306416112132; Thu, 26 May 2011 06:21:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.159.233 with HTTP; Thu, 26 May 2011 06:21:32 -0700 (PDT) In-Reply-To: <7BADE095-DEF5-4F6D-A5D3-A2BBAB362844@synchromedia.co.uk> References: <6AF0D2D6-EB8B-47BC-800C-F9AD87B21E0B@synchromedia.co.uk> <7BADE095-DEF5-4F6D-A5D3-A2BBAB362844@synchromedia.co.uk> From: Sasha Dolgy Date: Thu, 26 May 2011 15:21:32 +0200 Message-ID: Subject: Re: EC2 node adding trouble 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 Thu, May 26, 2011 at 3:12 PM, Marcus Bointon wrote: > I'd like to make sure I've got the right sequence of operations for addin= g a node without downtime. If I'm going from 2 to 3 nodes: > > 1 Calculate new initial_token values using the python script > 2 Change token values in existing nodes and restart them > 3 Install/configure new node > 4 Insert new node's token value > 5 Set new node to auto-bootstrap > 6 Start cassandra on new node > 7 Wait for the ring to rebalance > > With token changes (using values from the python script), it's clear that= all nodes will have some data moved. Does this mean that there's a possibi= lity of overlap between regions if token changes are not absolutely simulta= neous on all nodes? That sounds dangerous to me... Or shouldn't token value= s be changed on nodes containing data? > nodetool repair is good. when we add new nodes, we add a new one without specifying the new token. after everything is up and healthy, we determine new tokens and see if there is a need to renumber nodes. if we do, we do one at a time and wait until the nodetool repair is finished on one node before moving to another.... > Is there a corresponding sequence for removing nodes? I'm guessing draini= ng is involved. Turn the node off, remove the node from the ring using nodetool and removetoken .... i've found this to be the best problem-free way. Maybe it's better now ... http://blog.sasha.dolgy.com/2011/03/apache-cassandra-nodetool.html