[jira] [Updated] (CASSANDRA-5273) Hanging system after OutOfMemory. Server cannot die due to uncaughtException handling

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-5273:
--------------------------------------

    Attachment: 5273-v2.txt

Thinking about it more, I think adding a lock doesn't change anything.  System.exit already locks/synchronizes the important parts.  So we still have the deadlock problem, which we can hack around with timeouts but I'd rather not.

Patch attached against 1.2 to call System.exit from a new thread instead.
                
> Hanging system after OutOfMemory. Server cannot die due to uncaughtException handling
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5273
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5273
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.1
>         Environment: linux, 64 bit
>            Reporter: Ignace Desimpel
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: 0001-CASSANDRA-5273-add-timeouts-to-the-blocking-commitlo.patch, 0001-CASSANDRA-5273-add-timeouts-to-the-blocking-commitlo.patch, 5273-v2.txt, CassHangs.txt
>
>
> On out of memory exception, there is an uncaughtexception handler that is calling System.exit(). However, multiple threads are calling this handler causing a deadlock and the server cannot stop working. See http://www.mail-archive.com/user@cassandra.apache.org/msg27898.html. And see stack trace in attachement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira