[
https://issues.apache.org/jira/browse/CASSANDRA-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837609#comment-15837609
]
Stefan Podkowinski commented on CASSANDRA-13114:
------------------------------------------------
[~snazy], since you've been working on a couple of related issues
(CASSANDRA-12032, CASSANDRA-12033, CASSANDRA-12034, CASSANDRA-11937,
CASSANDRA-11818).. what would be your suggestion when it comes to back-porting
some of these to further stabilize memory management in 2.x and 3.0? Do you see
any issues updating netty to 4.0.42 on all branches, regardless of any
back-porting decisions for the listed tickets?
> 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)
