[
https://issues.apache.org/jira/browse/CASSANDRA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-5273:
---------------------------------------
Attachment: 0001-CASSANDRA-5273-add-timeouts-to-the-blocking-commitlo.patch
this is very hard to reproduce (and i have never seen it happen in any of our
clusters) so i simply added timeouts to the Thread#join methods in
CommitLog#shutdownBlocking
> 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: 1.2.5
>
> Attachments:
> 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
