Hi Aaron,
I tried again to add a node in the cluster. This time, I added the new node
in the seeds list after the bootstrap (the first time, I added the new node
in the seeds list before the bootstrap).
And it works !!!
Thanks Aaron.
Regards.
Jean Armel.
2013/2/22 Jean-Armel Luce
> Thanks
Thanks Aaron.
I shall investigate more next week about this.
regards.
Jean Armel
2013/2/22 aaron morton
> So, it looks that the repair is required if we want to add new nodes in
> our platform, but I don't understand why.
>
> Bootstrapping should take care of it. But new seed nodes do not boo
> So, it looks that the repair is required if we want to add new nodes in our
> platform, but I don't understand why.
Bootstrapping should take care of it. But new seed nodes do not bootstrap.
Check the logs on the nodes you added to see what messages have "bootstrap" in
them.
Anytime you are
Hi Aaron,
Thanks for your answer.
I apologize, I did a mistake in my 1st mail. The cluster was only 12 nodes
instead of 16 (it is a test cluster).
There are 2 datacenters b1 and s1.
Here is the result of nodetool status after adding a new node in the 1st
datacenter (dc s1):
root@node007:~# node
> 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 brin
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
