You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2017/02/02 13:59:51 UTC
[jira] [Comment Edited] (CASSANDRA-13114) 3.0.x: update netty
[ https://issues.apache.org/jira/browse/CASSANDRA-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849931#comment-15849931 ]
Robert Stupp edited comment on CASSANDRA-13114 at 2/2/17 1:58 PM:
------------------------------------------------------------------
I can, but would need some time.
EDIT: [~jjordan]'s suggestion makes sense. We already had an issue with a regression in Netty - just want to prevent a second upgrade-revert-upgrade-ticket ;)
was (Author: snazy):
I can, but would need some time.
> 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)