Try nodetool drain
Flushes all memtables for a node and causes the node to stop accepting write operations. Read operations will continue to work. This is typically used before upgrading a node to a new version of Cassandra.
On 30 Sep, 2010,at 10:15 AM, Justin Sanders <firstname.lastname@example.org> wrote:
I looked through the documentation but couldn't find anything. I was wondering if there is a way to manually mark a node "down" in the cluster instead of killing the cassandra process and letting the other nodes figure out the node is no longer up.
The reason I ask is because we are having an issue when we perform rolling restarts on the cluster. Basically read requests that come in on other nodes will block while they are waiting on the node that was just killed to be marked down. Before they realize the node is offline they will throw a TimedOutException.
If I could mark the node being down ahead of time this timeout period could be avoided. Any help is appreciated.