> After the bootstrap is finished in the new node, no data has been moved > automatically from the old nodes to this new node. What did nodetool ring say ?
> Please, could you tell me if we need to perform a nodetool repair after the > bootstrap of the new node ? You should not, bootstrap brings the node up with the data it should have. If you have any doubt though, running nodetool repair -pr on the new node cannot hurt. > 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 ?) Potentially yes. The simple thing would be to wait until a full repair cycle (on all nodes) to complete. Cheers ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 22/02/2013, at 3:44 AM, Jean-Armel Luce <jaluc...@gmail.com> wrote: > 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
