[
https://issues.apache.org/jira/browse/CASSANDRA-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-813:
---------------------------------------
Attachment: 813-v3.txt
It seems to me the simplest thing to do is add a threshold for the minimum
amount of time a GC must take before we log it. This cuts out the ParNew
logging but still retains CMS, or any future GC that spends too much time GCing.
> add some kind of logging of GC activity
> ---------------------------------------
>
> Key: CASSANDRA-813
> URL: https://issues.apache.org/jira/browse/CASSANDRA-813
> Project: Cassandra
> Issue Type: Task
> Reporter: Jonathan Ellis
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 0.6
>
> Attachments: 0001_log_gc_stats.txt, 813-v2.txt, 813-v3.txt
>
>
> "help, my node froze when i hammered it too hard" is a faq. before we have
> CASSANDRA-685 it would be nice to make it obvious what is going on w/ gc
> storms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
