[
https://issues.apache.org/jira/browse/CASSANDRA-8907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731344#comment-14731344
]
Johnny Miller edited comment on CASSANDRA-8907 at 9/4/15 8:15 PM:
------------------------------------------------------------------
[~JoshuaMcKenzie] [~eanujwa] I would advocate a default of disabled and when
disabled log out at INFO with the current behaviour. This should avoid breaking
any existing log monitoring or alarming anyone with a load of new WARN log
messages following a minor upgrade.
That way the onus is on the user to determine what level of pause for their
specific use case warrants a WARN log. As long as its clearly documented and in
the yaml, users should be aware of it when reviewing their config.
Maybe we should revisit the default level in a later major release following
feedback? Possibly default it to 200ms in 3.0?
was (Author: johnny15676):
[~JoshuaMcKenzie] [~eanujwa] I would advocate a default of disabled and when
disabled log out at INFO with the current behaviour. This should avoid breaking
any existing log monitoring or alarming anyone with a load of new WARN log
messages following a minor upgrade.
That way the onus is on the user to determine what level of pause for their
specific use case warrants a WARN log. As long as its clearly documented and in
the yaml, users should be aware of it when reviewing their config.
Maybe we should revisit the default level in a later major release following
feedback?
> 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)
