cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-218) exit if OOM occurs
Date Thu, 11 Jun 2009 12:49:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718431#action_12718431
] 

Hudson commented on CASSANDRA-218:
----------------------------------

Integrated in Cassandra #105 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/105/])
    system.exit on oome.  patch by jbellis; reviewed by Eric Evans for 


> exit if OOM occurs
> ------------------
>
>                 Key: CASSANDRA-218
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-218
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>         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.


Mime
View raw message