[
https://issues.apache.org/jira/browse/CASSANDRA-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399091#comment-13399091
]
Brandon Williams commented on CASSANDRA-3564:
---------------------------------------------
bq. There's no time limit on how long a flush will take and shutdown hooks can
take as long as needed to finish up so we have no idea when to "get more
forceful".
Nodetool is going to block until it's finished, at which point if the pid still
exists (I guess if jmx timed out or something) we just SIGKILL it.
> flush before shutdown so restart is faster
> ------------------------------------------
>
> Key: CASSANDRA-3564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3564
> Project: Cassandra
> Issue Type: New Feature
> Components: Packaging
> Reporter: Jonathan Ellis
> Assignee: David Alves
> Priority: Minor
> Fix For: 1.2
>
> Attachments: 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
