You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jan Dörrenhaus (JIRA)" <ji...@apache.org> on 2018/05/29 12:19:00 UTC
[jira] [Commented] (CASSANDRA-14355) Memory leak
[ https://issues.apache.org/jira/browse/CASSANDRA-14355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493457#comment-16493457 ]
Jan Dörrenhaus commented on CASSANDRA-14355:
--------------------------------------------
This issue has not been touched in almost two months now. It is the last open issue for 3.11.3, and 3.11.3 turns out to be critical for us, since CASSANDRA-14087 is a showstopper for us. Can this issue be fixed soon? Alternatively, is it possible to push it to a 3.11.4 release, and have 3.11.3 now?
> Memory leak
> -----------
>
> Key: CASSANDRA-14355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14355
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Debian Jessie, OpenJDK 1.8.0_151
> Reporter: Eric Evans
> Priority: Major
> Fix For: 3.11.3
>
> Attachments: 01_Screenshot from 2018-04-04 14-24-00.png, 02_Screenshot from 2018-04-04 14-28-33.png, 03_Screenshot from 2018-04-04 14-24-50.png
>
>
> We're seeing regular, frequent {{OutOfMemoryError}} exceptions. Similar to CASSANDRA-13754, an analysis of the heap dumps shows the heap consumed by the {{threadLocals}} member of the instances of {{io.netty.util.concurrent.FastThreadLocalThread}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org