You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/05/27 21:13:45 UTC
[jira] Updated: (CASSANDRA-115) Make cassandra crash-only
[ https://issues.apache.org/jira/browse/CASSANDRA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-115:
-------------------------------------
Attachment: 115.patch
Two places where I did a small amount of work besides simply deleting code:
AnalyticsContext.stopMonitoring now contains the timer code that used to be in shutdown
HttpRequestHandler.handleKillMe now starts a thread to shut down the JVM in one second instead of calling SS.shutdown
> 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.