cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5273) Hanging system after OutOfMemory. Server cannot die due to uncaughtException handling
Date Tue, 21 May 2013 15:49:25 GMT

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

Marcus Eriksson commented on CASSANDRA-5273:
--------------------------------------------

[~jbellis] you think the timeouts would be enough?
                
> 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, 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

Mime
View raw message