You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/08/12 03:12:16 UTC
[jira] Updated: (CASSANDRA-218) exit if OOM occurs
[ https://issues.apache.org/jira/browse/CASSANDRA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Greene updated CASSANDRA-218:
-------------------------------------
Component/s: Core
> exit if OOM occurs
> ------------------
>
> Key: CASSANDRA-218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-218
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.4
>
> Attachments: 218.patch
>
>
> The drawbacks to continuing running (generating internal errors in strange places) outweigh the benefits (maybe having the thread that OOM'd freed will allow us to serve some other requests successfully).
> I'm guessing that adding if (e instanceof OOME) { system.exit() } in our DefaultUncaughtExceptionHandler would do the trick.
> Only question is, would that happen before or after the XX:+HeapDumpOnOutOfMemoryError gets to fire?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.