cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2868) Native Memory Leak
Date Tue, 16 Aug 2011 17:01:28 GMT


Jonathan Ellis updated CASSANDRA-2868:

    Attachment: 2868-v3.txt

bq. I've never actually been able to get > 1 to happen, but we can add it to the logging

I'm sure it's possible w/ a small enough heap, especially since GCInspector is paused along
w/ everything else for STW collections (including new gen).

v3 attached to accomodate this and add durationPerCollection.

> Native Memory Leak
> ------------------
>                 Key: CASSANDRA-2868
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Daniel Doubleday
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 0.8.5
>         Attachments: 2868-v1.txt, 2868-v2.txt, 2868-v3.txt, 48hour_RES.png, 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