cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13114) Upgrade netty to 4.0.44 to fix memory leak with client encryption
Date Mon, 13 Feb 2017 22:04:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864543#comment-15864543
] 

Jeff Jirsa commented on CASSANDRA-13114:
----------------------------------------

Was this dire enough to go into 2.1 ?  Seems like a pretty high bar for a .17 release. 



> Upgrade netty to 4.0.44 to fix memory leak with client encryption
> -----------------------------------------------------------------
>
>                 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
>            Priority: Blocker
>             Fix For: 2.1.17, 2.2.9, 3.0.11, 3.11.0, 4.0
>
>         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)

Mime
View raw message