cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3564) flush before shutdown so restart is faster
Date Tue, 24 Jul 2012 21:21:35 GMT


Brandon Williams commented on CASSANDRA-3564:

bq. I suggest that we add flag that when enabled waits for the full flush for all tables and
maybe we don't even need the wait period since the user explicitely told that he wanted a
full flush and should be willing to wait. When the flag disabled reverts to the current setting
(flush only non-durable tables).

That sounds reasonable but I think we should have *some* kind of ceiling (10 minutes or something)
where we kill -9 it, just in case we ever have a bug that causes us not to exit (we've had
them before), so we don't hang the shutdown of the entire machine forever.
> flush before shutdown so restart is faster
> ------------------------------------------
>                 Key: CASSANDRA-3564
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Packaging
>            Reporter: Jonathan Ellis
>            Assignee: David Alves
>            Priority: Minor
>             Fix For: 1.2
>         Attachments: 3564.patch, 3564.patch
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message