[
https://issues.apache.org/jira/browse/CASSANDRA-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245398#comment-14245398
]
Benedict commented on CASSANDRA-8477:
-------------------------------------
Could you run the job that produces this error with the following VM options
(replacing \$file1 and \$file2 with an appropriate filename):
{noformat}
-XX:+UnlockDiagnosticVMOptions -XX:+PrintGCApplicationStoppedTime
-XX:+PrintGCDetails -XX:+PrintGCTimestamps -XX:LogFile=${file1}
-XX:+LogVMOutput -Xloggc:${file2}
{noformat}
and upload the resultant files for us to look at? The thing that's surprising
me is not the amount of garbage accumulation (although there may be something
to investigate there, and I'll peruse the heap dump at some point, the
histogram doesn't look super fishy), but the _length_ of the GC pause time. I
would like to understand why you had a 250s pause, because that is simply
insane, and not explicable from simple object accumulation.
> CMS GC can not recycle objects
> ------------------------------
>
> Key: CASSANDRA-8477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8477
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: 2.1.1 or 2.1.2-SNAPSHOT(after CASSANDRA-8459 resolved)
> Reporter: Philo Yang
> Attachments: cassandra.yaml, histo.txt, jstack.txt, system.log
>
>
> I have a trouble in my cluster that CMS full gc can not reduce the size of
> old gen. Days ago I post this problem to the maillist, people think it will
> be solved by tuning the gc setting, however it doesn't work for me.
> Then I saw a similar bug in CASSANDRA-8447, but [~benedict] think it is not
> related. With the jstack on
> https://gist.github.com/yangzhe1991/755ea2a10520be1fe59a, [~benedict] find a
> bug and resolved it in CASSANDRA-8459. So I build a latest version on 2.1
> branch and run the SNAPSHOT version on the nodes with gc trouble.
> However, there is still the gc issue. So I think opening a new tick and post
> more information is a good idea. Thanks for helping me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
