Return-Path: 
 <user-return-29424-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
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 18423DF1B
	for <apmail-cassandra-user-archive@www.apache.org>;
 Wed, 10 Oct 2012 09:30:22 +0000 (UTC)
Received: (qmail 25274 invoked by uid 500); 10 Oct 2012 09:30:19 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 24848 invoked by uid 500); 10 Oct 2012 09:30:14 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 24811 invoked by uid 99); 10 Oct 2012 09:30:12 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 09:30:12 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [209.85.212.44] (HELO mail-vb0-f44.google.com) (209.85.212.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 09:30:06 +0000
Received: by mail-vb0-f44.google.com with SMTP id fc26so183295vbb.31
        for <user@cassandra.apache.org>; Wed, 10 Oct 2012 02:29:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type
         :x-gm-message-state;
        bh=qcbKUuckIBoya7IIwtC46YxJXsB+ajklvqo4sA7jtwY=;
        b=LANDB6S/FOi1OG3qUbZVPFlp7USHjAdRxGp68Nx8Tl9qh7s4egLn9RrorXdUqVb0mw
         Fw6FtjgWt6rPmcHBUudoXq867HgMNpYljGT/OO9UTseds5779eZpQMvIuFdbXuyE0yTv
         CNmJah2Aw0cxjrGY8icotZsd9TJoQPT/kRofmM/N/I4PRLJsyT5f7jeVbrFutfSxor46
         ijHHxdUzIjqKXHReEZBgk8pSI1mlJE9pO4MIxn+CqQNSRYTrItPA/TkWiuF+DHSnBfLG
         Xo0SKRwqbq9DeGTu2SYAO5JgiQMb5i1R1PUl+aaLLhyPeeFAxjfgB18tEsReGJZA73UN
         c2Zw==
MIME-Version: 1.0
Received: by 10.52.72.42 with SMTP id a10mr11005769vdv.48.1349861384021; Wed,
 10 Oct 2012 02:29:44 -0700 (PDT)
Received: by 10.58.153.161 with HTTP; Wed, 10 Oct 2012 02:29:44 -0700 (PDT)
Date: Wed, 10 Oct 2012 11:29:44 +0200
Message-ID: 
 <CACyk+C+FXrMiF_oUPVQL6CX7-=4m=m+-i4tw2k-MRDkQ5BA4Lw@mail.gmail.com>
Subject: Upgrading hardware on a node in a cluster
From: Martin Koch <mak@issuu.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf307f362c4a683e04cbb118f7
X-Gm-Message-State: 
 ALoCoQmTjypHLXuP//L2WuuLLeA4eKXNuvdULOMK/hGkR6i8V3vGXoHAEw2rRoUs5xnNXNK+ZCKU
X-Virus-Checked: Checked by ClamAV on apache.org

--20cf307f362c4a683e04cbb118f7
Content-Type: text/plain; charset=ISO-8859-1

Hi List

I'd like to migrate my nodes in a cluster to new hardware, moving one node
at a time.

I'm running the cluster in Amazon, so I don't get to pick the ip number of
each host myself.

I'd like to decommision, say, the node with token 0, and bring that node up
on the new hardware (which will have a new IP number).

Can anyone provide me with a recipe for doing this? I've looked around and
read about nodetool move, which didn't make me much wiser.

Thanks for your help,
/Martin Koch - Issuu - Senior Systems Architect

--20cf307f362c4a683e04cbb118f7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi List<div><br></div><div>I&#39;d like to migrate my nodes in a cluster to=
 new hardware, moving one node at a time.=A0</div><div><br></div><div>I&#39=
;m running the cluster in Amazon, so I don&#39;t get to pick the ip number =
of each host myself.=A0</div>
<div><br></div><div>I&#39;d like to decommision, say, the node with token 0=
, and bring that node up on the new hardware (which will have a new IP numb=
er).=A0</div><div><br></div><div>Can anyone provide me with a recipe for do=
ing this? I&#39;ve looked around and read about nodetool move, which didn&#=
39;t make me much wiser.=A0</div>
<div><br></div><div>Thanks for your help,=A0</div><div>/Martin Koch - Issuu=
 - Senior Systems Architect</div>

--20cf307f362c4a683e04cbb118f7--