[
https://issues.apache.org/jira/browse/CASSANDRA-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860044#comment-15860044
]
Stefan Podkowinski commented on CASSANDRA-13114:
------------------------------------------------
I don't think this is critical enough for 2.1, as you have to have large enough
direct allocations through netty that will exhaust the memory between regular
CMS runs. So you don't necessarily have to run into this problem and there's an
easy workaround by not enabling disableexplicitgc (as described in
CASSANDRA-13126) or by simply replacing the netty jar with a new version.
But 2.2 and 3.0 - why not? Both are supported and it should be possible to do a
library updated there.
> 3.0.x: update netty
> -------------------
>
> Key: CASSANDRA-13114
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13114
> Project: Cassandra
> Issue Type: Bug
> Reporter: Tom van der Woerdt
> Assignee: Stefan Podkowinski
> Priority: Blocker
> Fix For: 3.0.11
>
> Attachments: 13114_netty-4.0.44_2.x-3.0.patch,
> 13114_netty-4.0.44_3.11.patch
>
>
> https://issues.apache.org/jira/browse/CASSANDRA-12032 updated netty for
> Cassandra 3.8, but this wasn't backported. Netty 4.0.23, which ships with
> Cassandra 3.0.x, has some serious bugs around memory handling for SSL
> connections.
> It would be nice if both were updated to 4.0.42, a version released this year.
> 4.0.23 makes it impossible for me to run SSL, because nodes run out of memory
> every ~30 minutes. This was fixed in 4.0.27.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
