[ https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066835#comment-13066835 ]
Daniel Doubleday commented on CASSANDRA-2868: --------------------------------------------- Looks good to me. Guess cassandra should just disable the inspector for now (probably make it jmx'able to start it manually) Thu Jul 14 09:39:26 CEST 2011: [anon]: 3234068 Thu Jul 14 17:22:45 CEST 2011: [anon]: 3266888 Fri Jul 15 09:33:53 CEST 2011: [anon]: 3269160 Mon Jul 18 09:54:29 CEST 2011: [anon]: 3270188 > 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 > Attachments: 2868-v1.txt, 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