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 D7CB92B4A for ; Wed, 27 Apr 2011 13:01:51 +0000 (UTC) Received: (qmail 50075 invoked by uid 500); 27 Apr 2011 13:01:48 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 50047 invoked by uid 500); 27 Apr 2011 13:01:48 -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 50036 invoked by uid 99); 27 Apr 2011 13:01:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Apr 2011 13:01:48 +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 (athena.apache.org: domain of watanabe.maki@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Apr 2011 13:01:42 +0000 Received: by bwz13 with SMTP id 13so1590585bwz.31 for ; Wed, 27 Apr 2011 06:01:20 -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:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=U2xHeHBZ9cmv1mSQ/Lo22XA5NtPowh5PCockoLYdbJ4=; b=WUNSsy2SNYlzrgtV79uDInPn6FxiZI/DHuO0p1T/0L32Kd18SBgMjAg7RdzBhvKc1O NftTanvheWj2jwxVtLpwPTGeWLpv+Eeu4GOzaGyDMKTPDhgjwod6VlSp1a1lGABgU7c8 1Bjg9uSu0MKF2vfeUx8bRP5rTqx46KESPVEXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=QRQZeOdbs6E8fREFLppyT4yMMsS3Zdbb5LRaMOdAUmDLHUtAA7veiWBp3Vf002O13H TJksGU2WM67p44Reb9lMuaTZvpMa2126aaX4nyHrsf/sVuHHSrEEoJkbO73CZ1JlAjyh 6kI6QTGg9NCVLnyTPL/h65R8KGtwdVUE6QA+E= MIME-Version: 1.0 Received: by 10.204.134.207 with SMTP id k15mr2019271bkt.135.1303909280711; Wed, 27 Apr 2011 06:01:20 -0700 (PDT) Received: by 10.204.152.20 with HTTP; Wed, 27 Apr 2011 06:01:20 -0700 (PDT) In-Reply-To: <576920.89036.qm@web112010.mail.gq1.yahoo.com> References: <576920.89036.qm@web112010.mail.gq1.yahoo.com> Date: Wed, 27 Apr 2011 22:01:20 +0900 Message-ID: Subject: Re: Expanding single node to 2 node cluster From: Maki Watanabe To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Why don't you just add new node to ring and removetoken of the bad one? 2011/4/27 maneela a > > Hi, > I had a 2 node cassandra cluster with replication factor 2 and OrderPrese= rvingPartitioner but we did not provide InitialToken in the=A0configuration= =A0files. One of the node was affected in the recent AWS EBS outage and had= been partitioned from cluster. However,=A0I continued to allowed all write= operations to other survived node because=A0I thought AWS could recovered = EBS issues with in 24 hours so Survived node might take care of propagating= 2nd replica from its hinted column family to the bad node when it recovere= d from EBS issues. Unfortunately AWS had taken longer than we expected almo= st 4 days. So instead of recovering 2nd node by playing hinted CF from node= 1, I did the following=A0sequence of events in order to get 2nd node back t= o cluster > 1) shut down cassandra service on good node > 2) removed all hinted CF files > 3) Taken EBS snapshot > 4) Launched new EBS volumes from above snapshot and mounted them on 2nd n= ode > 5) Also copied commitlogs from node1 to node2 > in other words, I cloned node1 and mounted on node2, my assumption is clu= ster with 2 nodes with replication 2 should likely be mirrored images > 6) brought up service on both nodes > 7) I am not seeing both IP address as part of ring when I ran nodetool co= mmand > root@domU-12-31-39-0F-CA-61:/mnt/logs/cassandra# nodetool -h localhost ri= ng > Address =A0 =A0 =A0 Status =A0 =A0 Load =A0 =A0 =A0 =A0 =A0Range =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ring > 10.193.201.139Up =A0 =A0 =A0 =A0 434.77 GB =A0 =A0 RVtMj8gWiKG0baPy =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<--| > root@ip-10-196-107-47:/data/cassandra/data/system# nodetool -h localhost = ring > Address =A0 =A0 =A0 Status =A0 =A0 Load =A0 =A0 =A0 =A0 =A0Range =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ring > 10.193.201.139Up =A0 =A0 =A0 =A0 434.77 GB =A0 =A0 RVtMj8gWiKG0baPy =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<--| > > I guess this behavior is happening because both nodes are having same dat= a including Locationinfo CF and commit logs as well. Can someone direct me = what should be done here to get both IPs as part of ring? > Thanks > niru > -- w3m