On Tue, May 22, 2012 at 3:00 AM, aaron morton <aa...@thelastpickle.com> wrote: > 1) Isolating the node from the cluster to stop write activity. You can > either start the node with the -Dcassandra.join_ring=false JVM option or > use nodetool disablethrift and disablegossip to stop writes. Note that this > will not stop existing Hinted Handoff sessions which target the node.
As a result of the last caveat here, I recommend either restarting the node with the join_ring as false or using iptables to firewall off ports 7000 and 9160. If you want to be sure that you have stopped write activity right now, nuking these ports from orbit is the only way to be sure. disablethrift/disablegossip as currently implemented are not sufficient for this goal. https://issues.apache.org/jira/browse/CASSANDRA-4162 =Rob -- =Robert Coli AIM>ALK - rc...@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb
