[
https://issues.apache.org/jira/browse/CASSANDRA-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814421#comment-15814421
]
Stefan Podkowinski commented on CASSANDRA-13114:
------------------------------------------------
Netty 4.0.23 has been introduced in CASSANDRA-7761 and is used since 2.1.1.
Looking at the [4.0.27 release
notes|http://netty.io/news/2015/04/02/4-0-27-Final.html] I assume that
[#3567|https://github.com/netty/netty/issues/3567] fixes the memory issue
you're referring to? If I read the ticket correctly, the bug does not manifest
in 4.0.23, but only after updating to 4.0.25/26. Can you link the actual issue
that makes you believe 4.0.23 is affected in case there's something I'm missing
here?
> 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
>
> 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.4#6332)
