Details
-
New Feature
-
Status: Resolved
-
Low
-
Resolution: Later
-
None
-
None
Description
Cassandra handles flush in its shutdown hook for durable_writes=false CFs (otherwise we're guaranteed to lose data) but leaves it up to the operator otherwise. I'd rather leave it that way to offer these semantics:
- cassandra stop = shutdown nicely [explicit flush, then kill -int]
- kill -INT = shutdown faster but don't lose any updates [current behavior]
- kill -KILL = lose most recent writes unless durable_writes=true and batch commits are on [also current behavior]
But if it's not reasonable to use nodetool from the init script then I guess we can just make the shutdown hook flush everything.