You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2016/06/19 15:35:05 UTC
[jira] [Updated] (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:all-tabpanel ]
Robert Stupp updated CASSANDRA-12034:
-------------------------------------
Status: Patch Available (was: Open)
Trivial patch for this:
||trunk|[branch|https://github.com/apache/cassandra/compare/trunk...snazy:12034-netty-oom-special-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-12034-netty-oom-special-trunk-testall/lastSuccessfulBuild/]|[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-12034-netty-oom-special-trunk-dtest/lastSuccessfulBuild/]
> 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
>
> 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)