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 jaluce06@gmail.com designates
 209.85.212.43 as permitted sender)
MIME-Version: 1.0
Date: Thu, 21 Feb 2013 15:44:55 +0100
Message-ID: 
 <CALnckSqsKnfXnUt5AkrXvKT5C9buBRptcuXpyJHx5uNmh=cn5w@mail.gmail.com>
Subject: Adding new nodes in a cluster with virtual nodes
From: Jean-Armel Luce <jaluce06@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=bcaec54fb0fc44795904d63d1e4e

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

Hello,

We are using Cassandra 1.2.0.
We have a cluster of 16 physical nodes, each node has 256 virtual nodes.
We want to add 2 new nodes in our cluster : we follow the procedure as
explained here :
http://www.datastax.com/docs/1.2/operations/add_replace_nodes.

After starting 1 of the new node, we can see that this new node has 256
tokens ==>looks good
We can see that this node is in the ring (using nodetool status) ==> looks
good
After the bootstrap is finished in the new node, no data has been moved
automatically from the old nodes to this new node.


However, when we send insert queries in our cluster, the new node accepts
to insert the new rows.

Please, could you tell me if we need to perform a nodetool repair after the
bootstrap of the new node ?
What happens if we perform a nodetool cleanup in the old nodes before doing
the nodetool repair ? (Is there a risk of loosing some data ?)

Regards.

Jean Armel

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

Hello,<br><br>We are using Cassandra 1.2.0.<br>We have a cluster of 16 phys=
ical nodes, each node has 256 virtual nodes.<br>We want to add 2 new nodes =
in our cluster : we follow the procedure as explained here : <a href=3D"htt=
p://www.datastax.com/docs/1.2/operations/add_replace_nodes">http://www.data=
stax.com/docs/1.2/operations/add_replace_nodes</a>.<br>
<br>After starting 1 of the new node, we can see that this new node has 256=
 tokens =3D=3D&gt;looks good<br>We can see that this node is in the ring (u=
sing nodetool status) =3D=3D&gt; looks good<br>After the bootstrap is finis=
hed in the new node, no data has been moved automatically from the old node=
s to this new node.<br>
<br><br>However, when we send insert queries in our cluster, the new node a=
ccepts to insert the new rows.<br><br>Please, could you tell me if we need =
to perform a nodetool repair after the bootstrap of the new node ? <br>
What happens if we perform a nodetool cleanup in the old nodes before doing=
 the nodetool repair ? (Is there a risk of loosing some data ?)<br><br>Rega=
rds.<br><br>Jean Armel<br>

--bcaec54fb0fc44795904d63d1e4e--