[
https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063770#comment-13063770
]
Daniel Doubleday commented on CASSANDRA-2868:
---------------------------------------------
Next: [anon]: 3675224 (+47616KB in 1 day)
bq. Is your data size constant? If not you are probably seeing growth in the
index samples and bloom filters.
Well no - the data size is increasing. But I thought that index and bf is good
old plain java heap no? JVM heap stats are really relaxed. Yet I think that
doesn't really matter because what we are seeing is an ever increasing rss mem
consumption even though we have -Xmx3G and -Xms3G and mlockall (pmap shows
these 3G as one block). So something seems to be constantly allocating native
mem that has nothing to do with java heap.
> Native Memory Leak
> ------------------
>
> Key: CASSANDRA-2868
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2868
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.6
> Reporter: Daniel Doubleday
> Priority: Minor
>
> 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: http://www.atlassian.com/software/jira
