Yes, that is what would happen; some anti entropy mechanism would have to perform the replication after the fact (hinted handoff, read repair, manual repair etc).
For most things, it's better to rely on the dynamic endpoint snitch and some sort of dynamic load balancing from the client (see: https://github.com/rantav/hector/blob/master/core/src/main/java/me/prettyprint/cassandra/connection/DynamicLoadBalancingPolicy.java) to automatically route around busy nodes. I don't remember when the referenced nodetool command was added; for older versions, a similar effect can be achieved using iptables or similar tools. On Thu, Mar 8, 2012 at 12:56 PM, Karl Hiramoto <k...@hiramoto.org> wrote: > On 03/08/12 21:40, Edward Capriolo wrote: > >> On Thu, Mar 8, 2012 at 1:43 PM, Feng Qu<mail...@gmail.com> wrote: >> >>> Hello, is there a way to take one node out of ring and running a major >>> compaction? >>> >>> Feng Qu >>> >> http://www.jointhegrid.com/**highperfcassandra/?p=187<http://www.jointhegrid.com/highperfcassandra/?p=187> >> >> > What are the drawbacks to disable thrift and gossip? So you take a node > offine to do repair/compact, but then assuming writes are comming into your > cluseter at a steady rate, you have missing writes that need to be repaired > in the node that was offline? Is that what would happen? > > -- > Karl >
