Benedict created CASSANDRA-15214:

             Summary: OOMs caught and not rethrown
                 Key: CASSANDRA-15214
             Project: Cassandra
          Issue Type: Bug
          Components: Messaging/Client, Messaging/Internode
            Reporter: Benedict

Netty (at least, and perhaps elsewhere in Executors) catches all exceptions, so 
presently there is no way to ensure that an OOM reaches the JVM handler to 
trigger a crash/heapdump.

It may be that the simplest most consistent way to do this would be to have a 
single thread spawned at startup that waits for any exceptions we must 
propagate to the Runtime.

We could probably submit a patch upstream to Netty, but for a guaranteed future 
proof approach, it may be worth paying the cost of a single thread.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to