cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-10548) OOM in Ref#GlobalState
Date Mon, 19 Oct 2015 13:12:05 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benedict resolved CASSANDRA-10548.
----------------------------------
    Resolution: Duplicate

This was fixed in 2.1.7, see the linked ticket

> OOM in Ref#GlobalState
> ----------------------
>
>                 Key: CASSANDRA-10548
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10548
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Maxim Podkolzine
>         Attachments: Screenshot.png
>
>
> Cassandra eats up all memory (at one time 24Gb) and crashes with OOM.
> I was able to analyze one instance of hprof and concluded that ~3Gb were referenced by
GlobalState instances, mostly ConcurrentLinkedQueues (see the details in screenshot attached).
I can provide the hprof if necessary.
> I noticed that in 2.2 the source code changed in this place. Can you confirm it's better
in 2.2 in terms of memory management?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message