[
https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073636#comment-13073636
]
Sylvain Lebresne commented on CASSANDRA-2868:
---------------------------------------------
Comments on v2:
* Couldn't we estimate the reclaimed size by recording the last memory used
(that would need to be the first thing we do in logGCResults so that we record
it each time) ?
* Wouldn't it be worth indicating that how many collection have been done since
last log message if it's > 1, since it can (be > 1).
* Nit: especially if we decide to keep the last memory used, it may be more
efficient (in cleaner imho) to have just one HashMap of string -> GCInfo where
GCInfo would be a small struct with times, counts and usedMemory. Not that it
is very performance sensitive...
> 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, 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: http://www.atlassian.com/software/jira
