Tokens can change, so IP is used for node identification, e.g. for hinted handoff.
On Wed, Nov 18, 2009 at 1:00 PM, Ramzi Rabah <rra...@playdom.com> wrote: > Hey Jonathan, why should a replacement node keep the same IP > address/DNS name as the original node? Wouldn't having the same token > as the node that went down be sufficient (provided that you did the > steps above of copying the data from the 2 neighboring nodes)? > > On Wed, Nov 18, 2009 at 10:30 AM, Jonathan Ellis <jbel...@gmail.com> wrote: >> On Wed, Nov 18, 2009 at 12:05 PM, Jon Graham <sjclou...@gmail.com> wrote: >>> Hello Everyone, >>> >>> Is there a recommended backup/restore procedure to be able to recover a >>> failed node? >> >> Until tickets 193 and 520 are done, the easiest thing is to copy all >> the sstables from the other nodes that have replicas for the ranges it >> is responsible for (e.g. for replication factor of 3 on rack unaware >> partitioner, the nodes before it and the node after it on the right >> would suffice), and then run nodeprobe cleanup to clear out the >> excess. >> >>> How does Cassandra keep track of a node's identity? >> >> It stores it in the system table. >> >>> Should a replacement node keep the same IP address/DNS name as the original >>> node? >> >> Yes. >> >>> Does a node still receive data while a nodeprobe snapshot" command runs? >> >> Yes. >> >> -Jonathan >> >
