cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13114) 3.0.x: update netty
Date Wed, 25 Jan 2017 13:09:26 GMT

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

Robert Stupp commented on CASSANDRA-13114:
------------------------------------------

No objections regarding a _minor_ netty upgrade, if that solves real SSL issues / an existing
bug.  I'd just be very careful with dependency changes since 4.0.37 introduced a couple of
issues.
Would setting {{-XX:MaxDirectMemorySize=SomeBigValue}} help in this case?
However, I do object introducing the new stuff from CASSANDRA-12032 in 2.2 or 3.0, because
it is a new thing, which is disabled by default in 3.x.


> 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)

Mime
View raw message