[
https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063463#comment-13063463
]
Chris Burroughs commented on CASSANDRA-2868:
--------------------------------------------
At one point I was convinced this was a JVM bug and opened
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7037080 After seeing how
totally broken NIO is after CASSANDRA-2654 I'm no longer sure of anything.
I was going to start a survey on the user list after the summit to see if any
OS/jvm level pattern could be found, since clearly it doesn't happen to
everyone in all cases.
> 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
