You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Abdul Patel (JIRA)" <ji...@apache.org> on 2018/06/03 14:55: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=16499444#comment-16499444 ]
Abdul Patel commented on CASSANDRA-14355:
-----------------------------------------
I have seen nodetool info reporting high memory usage after a weeks of upgrading t0 3.11.2, i rebooted all nodes 1 week no issues, later agian same , no errors in errorlog .
is this related to this issue?
> 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