Return-Path: X-Original-To: apmail-cassandra-dev-archive@www.apache.org Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 45FCA105B9 for ; Fri, 21 Jun 2013 21:52:46 +0000 (UTC) Received: (qmail 21599 invoked by uid 500); 21 Jun 2013 21:52:42 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 21579 invoked by uid 500); 21 Jun 2013 21:52:42 -0000 Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list dev@cassandra.apache.org Received: (qmail 21548 invoked by uid 99); 21 Jun 2013 21:52:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 21:52:42 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Robin.Mahony@netapp.com designates 216.240.18.76 as permitted sender) Received: from [216.240.18.76] (HELO mx11.netapp.com) (216.240.18.76) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 21:52:37 +0000 X-IronPort-AV: E=Sophos;i="4.87,915,1363158000"; d="scan'208,217";a="28367529" Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx11-out.netapp.com with ESMTP; 21 Jun 2013 14:52:17 -0700 Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Fri, 21 Jun 2013 14:52:17 -0700 From: "Mahony, Robin" To: "dev@cassandra.apache.org" , "user@cassandra.apache.org" Subject: Re: [Cassandra] Replacing a cassandra node with one of the same IP Thread-Topic: Re: [Cassandra] Replacing a cassandra node with one of the same IP Thread-Index: Ac5uyQGuYc874dzhSMSyW7V8XU3AhA== Date: Fri, 21 Jun 2013 21:52:16 +0000 Message-ID: <35200C7887BDD94DA24A304607C50B581266AC6E@SACEXCMBX01-PRD.hq.netapp.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: multipart/alternative; boundary="_000_35200C7887BDD94DA24A304607C50B581266AC6ESACEXCMBX01PRDh_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_35200C7887BDD94DA24A304607C50B581266AC6ESACEXCMBX01PRDh_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please note that I am currently using version 1.2.2 of Cassandra. Also we = are using virtual nodes. My question mainly stems from the fact that the nodes appear to be aware th= at the node uuid changes for the IP (from reading the logs), so I am just w= ondering if this means the hinted handoffs are also updated to reflect the = new Cassandra node uuid. If that was the case, I would not think a nodetool= cleanup would be necessary. ----- Forwarded Message ----- From: Robert Coli > To: user@cassandra.apache.org; Emalayan V= airavanathan > Sent: Thursday, 20 June 2013 11:40 AM Subject: Re: [Cassandra] Replacing a cassandra node On Thu, Jun 20, 2013 at 10:40 AM, Emalayan Vairavanathan > wrote: > In the case where replace a cassandra node (call it node A) with another = one > that has the exact same IP (ie. during a node failure), what exactly shou= ld > we do? Currently I understand that we should at least run "nodetool > repair". If you lost the data from the node, then what you want is "replace_token." If you didn't lose the data from the node (and can tolerate stale reads until the repair completes) you want to start the node with auto_bootstrap set to false and then repair. =3DRob --_000_35200C7887BDD94DA24A304607C50B581266AC6ESACEXCMBX01PRDh_--