[
https://issues.apache.org/jira/browse/CASSANDRA-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837758#comment-15837758
]
Tom van der Woerdt commented on CASSANDRA-13114:
------------------------------------------------
4.0.39 has been tested pretty well with 3.x by now, so it should be relatively
safe (much safer than, say, 3.0.36, which not only hasn't been tested, but also
won't get the attention that 3.0.39 would get if it is used by both 3.0 and
3.x). Definitely don't pick 4.1!
As for setting MaxDirectMemorySize: it was set to 20GB when I filed this
ticket. No luck :)
Side-note: CASSANDRA-13126 is a related issue, on clusters with SSL enabled
even non SSL clients may be impacted due to this netty issue.
> 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)
