[
https://issues.apache.org/jira/browse/CASSANDRA-8907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737206#comment-14737206
]
Joshua McKenzie edited comment on CASSANDRA-8907 at 9/9/15 5:06 PM:
--------------------------------------------------------------------
2.1 branch link attached. Rebased and fixed a bug in the stat printing logic.
Edit: [~achowdhe]: If I could get a review of that branch and a +1 from you
(assuming the code looks good), I'll go ahead and get this committed. Thanks!
was (Author: joshuamckenzie):
2.1 branch link attached. Rebased and fixed a bug in the stat printing logic.
> Raise GCInspector alerts to WARN
> --------------------------------
>
> Key: CASSANDRA-8907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8907
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Adam Hattrell
> Assignee: Amit Singh Chowdhery
> Labels: patch
> Attachments: cassnadra-8907.patch
>
>
> I'm fairly regularly running into folks wondering why their applications are
> reporting down nodes. Yet, they report, when they grepped the logs they have
> no WARN or ERRORs listed.
> Nine times out of ten, when I look through the logs we see a ton of ParNew or
> CMS gc pauses occurring similar to the following:
> INFO [ScheduledTasks:1] 2013-03-07 18:44:46,795 GCInspector.java (line 122)
> GC for ConcurrentMarkSweep: 1835 ms for 3 collections, 2606015656 used; max
> is 10611589120
> INFO [ScheduledTasks:1] 2013-03-07 19:45:08,029 GCInspector.java (line 122)
> GC for ParNew: 9866 ms for 8 collections, 2910124308 used; max is 6358564864
> To my mind these should be WARN's as they have the potential to be
> significantly impacting the clusters performance as a whole.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
