Bootstrapping uses the same mechanisms as a repair to streams data from other nodes. This can be a heavy weight process and you may want to control when it starts.
Joining the ring just tells the other nodes you exists and this is your token. A On 10/03/2011, at 9:27 AM, mcasandra wrote: > Thanks! > > aaron morton wrote: >> >> >> The issue I think you and Patrik are seeing occurs when you *remove* nodes >> from the ring. The ring does not know if they are up or down. E.g. you >> have a ring of 3 nodes, and add a keyspace with RF 3. Then for whatever >> reason 2 nodes are removed from the ring. When bootstrapping a node into >> this ring it will fail because it detects the cluster does not have enough >> *endpoints* (different to up nodes) to support the keyspace. >> >> > What causes a node to remove? All I did was kill -9 and then sudo cassandra > to start the node. > > > >> IMHO bootstrapping is the process of pulling data the *new* node is >> responsible for from other nodes in the ring. This is different to joining >> the ring. >> > > How is this different than joining the ring? It will be good to see some > example and the difference. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/problem-with-bootstrap-tp6127315p6155334.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com.
