[ https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Burroughs updated CASSANDRA-2868: --------------------------------------- Attachment: 48hour_RES.png 48 hours under production load after C* had already been running for a few days. Two on the left have GCInspector enabled. The two on the right do not. (Note that the scale on the lower right one reflects a change of only 10s of bytes.) So it looks like victory to me. > Native Memory Leak > ------------------ > > Key: CASSANDRA-2868 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2868 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Daniel Doubleday > Assignee: Brandon Williams > Priority: Minor > Fix For: 0.8.3 > > Attachments: 2868-v1.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: http://www.atlassian.com/software/jira