You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2016/06/21 15:02:57 UTC

[jira] [Commented] (CASSANDRA-12034) Special handling for Netty's direct memory allocation failure

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

T Jake Luciani commented on CASSANDRA-12034:
--------------------------------------------

I think we should be careful here since this is adding a new kind of error for users to think about.

How is this not a destabilizing condition?  We don't know if it's this users response or another that's taking up the memory, or when it will resolve.  
  

> Special handling for Netty's direct memory allocation failure
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-12034
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12034
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>             Fix For: 3.x
>
>
> With CASSANDRA-12032, Netty throws a {{io.netty.util.internal.OutOfDirectMemoryError}} if there's not enough off-heap memory for the response buffer. We can easily handle this situation and return an error. This is not a condition that destabilizes the system and should therefore not passed to {{JVMStabilityInspector}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)