[CASSANDRA-8907] Raise GCInspector alerts to WARN

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.10
• Labels: patch
• Assignee: Amit Singh Chowdhery
• Reporter: Adam Hattrell

Authors

Amit Singh Chowdhery

Reviewers

Joshua McKenzie

• Created: 04/Mar/15 18:07
• Updated: 16/Apr/19 09:31
• Resolved: 11/Sep/15 17:20

Description

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.

Issue Links

• relates to: CASSANDRA-11644 gc_warn_threshold_in_ms is not applied when it's greater than MIN_LOG_DURATION(200ms)
• links to: 2.1 branch