cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12034) Special handling for Netty's direct memory allocation failure
Date Fri, 24 Jun 2016 16:04:16 GMT

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

Robert Stupp commented on CASSANDRA-12034:
------------------------------------------

Alright - now the patch just adds two calls to {{JVMStabilityInspector}}.
Also took the freedom to remove the netty settings from {{cassandra-env}} and moved it to
{{jvm.options}}, also added some text about {{-XX:MaxDirectMemorySize}}.

> 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
>              Labels: doc-impacting
>             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)

Mime
View raw message