[
https://issues.apache.org/jira/browse/CASSANDRA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713703#action_12713703
]
Jonathan Ellis edited comment on CASSANDRA-115 at 5/27/09 12:24 PM:
--------------------------------------------------------------------
It's worth noting that the shutdown code was mostly unused anyway, since the
only place that calls it was HttpRH. The recommended way to stop a cassandra
node from the command line has always been "kill."
was (Author: jbellis):
It's worth noting that the shutdown code is mostly untested, since the only
place that calls it was HttpRH. The recommended way to stop a cassandra node
from the command line has always been "kill."
> Make cassandra crash-only
> -------------------------
>
> Key: CASSANDRA-115
> URL: https://issues.apache.org/jira/browse/CASSANDRA-115
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Fix For: 0.4
>
> Attachments: 115.patch
>
>
> The only benefit to shutdown is flushing memtables cleanly which will save a
> little time on restart. This can be done w/o the full shutdown harness which
> only "mostly" works anyway. CASSANDRA-76 will give us a better way to force
> flushes but it is not strictly necessary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
