cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2868) Native Memory Leak
Date Mon, 01 Aug 2011 00:57:10 GMT


Brandon Williams commented on CASSANDRA-2868:

I created three isolated nodes, all with a hack of setting the inspector interval to 1ms applied
(not the tightest loop, but good enough and easy.)  One of the nodes had the inspector disabled
entirely (the control), one was vanilla, and one had v2 applied.  After starting them up with
a 128M heap and letting them run for a few minutes, here are the results:


I think it's safe to say doesn't share the leak.

> 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.3
>         Attachments: 2868-v1.txt, 2868-v2.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