[
https://issues.apache.org/jira/browse/CASSANDRA-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851522#comment-15851522
]
Tom van der Woerdt commented on CASSANDRA-13114:
------------------------------------------------
I've deployed [~mshuler]'s snapshot build to most nodes in the cluster that
previously experienced this issue, and re-enabled TLS on a few hundred clients.
The nodes still on 3.0.10 quickly showed memory issues, while the nodes on
3.0.11-SNAPSHOT were happy.
So I upgraded the remaining nodes and enabled TLS on another ~50000 clients,
many many more than I originally needed to cause problems.
Nothing broke.
So basically I can confirm that this patch fixes the problem, and at least for
my test cases (one involves fairly heavy use of QUORUM reads and writes)
doesn't appear to introduce new ones. I wouldn't take that over good
dtests/utests, but it's a useful data point to have.
> 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
> 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)
