Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of gdusbabek@gmail.com
 designates 74.125.82.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type:content-transfer-encoding;
        b=iFv4RufJ/0kXb+PQ1hAy3iZ7NEY9hf1wsgNHzleoZzsB1We7JSWvAOb+jK3AC0gsoA
         kyGuVP2OvL5+ieY7xezFTLJN7I5mvrpgOyLfQnTu1Crio3ZNuOrTbO7gIwqq0ltTQFM7
         xI3u9IT8lwS3wcyDiPgfFgvCYPar6n7SLpcKI=
MIME-Version: 1.0
Reply-To: gdusbabek@gmail.com
In-Reply-To: <AANLkTi=7kwbZBAcn9R4on0XGApdzkbhBqS-+9NHGTWTt@mail.gmail.com>
References: <AANLkTi=7kwbZBAcn9R4on0XGApdzkbhBqS-+9NHGTWTt@mail.gmail.com>
Date: Mon, 4 Oct 2010 07:38:52 -0500
Message-ID: <AANLkTikU2crfcbu5x9_57dCL7+xHBn-M9Fp45oTsidj2@mail.gmail.com>
Subject: Re: Hardware change of a node in the cluster
From: Gary Dusbabek <gdusbabek@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It should work this way:

1. Move your data to the new node (scp, etc.)
2. Make sure the new node is configured to use the same token as the new no=
de.
3. Stand up the new node.
4. Turn off the old node.

If your environment is volatile, it's probably best to run `nodetool
repair` on the new node.

Gary.


On Mon, Oct 4, 2010 at 04:58, Utku Can Top=E7u <utku@topcu.gen.tr> wrote:
> Hey All,
>
> Recently I've tried to upgrade (hw upgrade) one of the nodes in my cassan=
dra
> cluster from ec2-small to ec2-large.
>
> However, there were problems and since the IP of the new instance was
> different from the previous instance. The other nodes didnot recognize it=
 in
> the ring.
>
> So what should be the best practice for a complete hardware change of one
> node in the cluster while keeping the data that it has.
>
> Regards,
>
> Utku
>