Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "Operations" page has been changed by Chris Goffinet. http://wiki.apache.org/cassandra/Operations?action=diff&rev1=19&rev2=20 -------------------------------------------------- 1. (Advanced approach) Bring up a replacement node with the same IP and token as the old, and run `nodeprobe repair`. Until the repair process is complete, clients reading only from this node may get no data back. Using a higher !ConsistencyLevel on reads will avoid this. You can obtain the old token by running `nodeprobe ring` on any live node to find the token (Unless there was some kind of outage, and the others came up but not the down one). - The reason why you run `nodeprobe removetoken` on all live nodes is so that the Hinted Handoff can stop collecting writes for the failed node. + The reason why you run `nodeprobe removetoken` on all live nodes is so that Hinted Handoff can stop collecting writes for the dead node. == Backing up data == Cassandra can snapshot data while online using `nodeprobe snapshot`. You can then back up those snapshots using any desired system, although leaving them where they are is probably the option that makes the most sense on large clusters.
