Assuming you aren't changing the RC, the normal bootstrap process takes care of all the problems like that, making sure things work correctly.
Most importantly, if something fails (either the new node or any of the existing nodes) you can recover from it. Just don't connect clients directly to that new node until it's fully in the ring. On Tue, Feb 15, 2011 at 5:05 PM, mcasandra <mohitanch...@gmail.com> wrote: > > Is there a way to let the new node join cluster in the background and make > it > live to clients only after it has finished with node repair, syncing data > etc. and in the end sync keys or trees that's needed before it's come to > life. I know it can be tricky since it needs to be live as soon as it > steals > the keys. > > This ways we know we are adding nodes only when we think it's all ready. > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Data-distribution-tp6025869p6029708.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >
