cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2868) Native Memory Leak
Date Fri, 15 Jul 2011 16:25:00 GMT


Chris Burroughs commented on CASSANDRA-2868:

I interpreted Daniel's "this" to be the 2868-v1.txt patch (or something equivalent) with cassandra.enable_gc_inspector=false.
 I did not find -XX:MaxDirectMemorySize to be helpful.

> Native Memory Leak
> ------------------
>                 Key: CASSANDRA-2868
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.6
>            Reporter: Daniel Doubleday
>            Priority: Minor
>         Attachments: 2868-v1.txt, low-load-36-hours-initial-results.png
> We have memory issues with long running servers. These have been confirmed by several
users in the user list. That's why I report.
> The memory consumption of the cassandra java process increases steadily until it's killed
by the os because of oom (with no swap)
> Our server is started with -Xmx3000M and running for around 23 days.
> pmap -x shows
> Total SST: 1961616 (mem mapped data and index files)
> Anon  RSS: 6499640
> Total RSS: 8478376
> This shows that > 3G are 'overallocated'.
> We will use BRAF on one of our less important nodes to check wether it is related to
mmap and report back.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message