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 9EE7D10CEF for ; Sun, 2 Feb 2014 18:49:20 +0000 (UTC) Received: (qmail 55862 invoked by uid 500); 2 Feb 2014 18:49:17 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55771 invoked by uid 500); 2 Feb 2014 18:49:17 -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 55763 invoked by uid 99); 2 Feb 2014 18:49:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Feb 2014 18:49:16 +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 (nike.apache.org: domain of joshua_sholes@cable.comcast.com designates 69.241.43.119 as permitted sender) Received: from [69.241.43.119] (HELO cable.comcast.com) (69.241.43.119) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Feb 2014 18:49:08 +0000 Received: from ([24.40.56.115]) by pacdcavout01.cable.comcast.com with ESMTP id 97wm3m1.81796422; Sun, 02 Feb 2014 13:48:45 -0500 Received: from PACDCEXMB22.cable.comcast.com ([fe80::f887:1b71:477f:d14b]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.03.0158.001; Sun, 2 Feb 2014 13:48:45 -0500 From: "Sholes, Joshua" To: "user@cassandra.apache.org" Subject: One of my nodes is in the wrong datacenter - help! Thread-Topic: One of my nodes is in the wrong datacenter - help! Thread-Index: AQHPIEdmp1sQWqxsokOC7ST9ZsCsYQ== Date: Sun, 2 Feb 2014 18:48:45 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [68.87.16.247] Content-Type: multipart/alternative; boundary="_000_CF13FD3BC936JoshuaSholescablecomcastcom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_CF13FD3BC936JoshuaSholescablecomcastcom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable All, I had a node in my 8-node production 1.2.8 cluster have a serious problem a= nd need to be removed and rebuilt. However, after doing nodetool removeno= de and then bootstrapping a new node on the same IP address, the new node s= omehow ended up with a different datacenter name (the rest of the nodes are= in dc $NAME, and the new one is in dc $NAME6934724 =97 as in, a string of = seemingly random numbers appended to the correct name). How can I force i= t to change DC names back to what it should be? I=92m working with 500+GB per node here so bootstrapping it again is not a = huge issue, but I=92d prefer to avoid it anyway. I am NOT able to change t= he node=92s IP address at this time so I=92m stuck with bootstrapping a new= node in the same place, which my gut feeling tells me might be part of the= problem. Any insight anyone can give me is highly appreciated. Thanks, -- Josh Sholes --_000_CF13FD3BC936JoshuaSholescablecomcastcom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <5B183C6A1234B24B833D992221EC9525@cable.comcast.com> Content-Transfer-Encoding: quoted-printable

All,

I had a node in my 8-node production 1.2.8 cluster have a serious problem a= nd need to be removed and rebuilt. However, after doing nodetool rem= ovenode and then bootstrapping a new node on the same IP address, the new n= ode somehow ended up with a different datacenter name (the rest of the nodes are in dc $NAME, and the new one is= in dc $NAME6934724 =97 as in, a string of seemingly random numbers appende= d to the correct name). How can I force it to change DC names back t= o what it should be?

I=92m working with 500+GB per node here so bootstrapping it again is no= t a huge issue, but I=92d prefer to avoid it anyway. I am NOT able to= change the node=92s IP address at this time so I=92m stuck with bootstrapp= ing a new node in the same place, which my gut feeling tells me might be part of the problem.

Any insight anyone can give me is highly appreciated.

Thanks,

Josh Sholes

--_000_CF13FD3BC936JoshuaSholescablecomcastcom_--