cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Hattrell (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8907) Raise GCInspector alerts to WARN
Date Mon, 07 Sep 2015 07:25:46 GMT


Adam Hattrell commented on CASSANDRA-8907:

Even for the slackest user requirements - I've never a system that a seconds pause didn't
kill it.  I would strongly advocate for warning at least at that level.

I would probably advocate 500ms as being significantly poor.  I've seen a few users that manage
at 200ms.  

I'd like 500ms in current and then 200 in 3.0.  I'd settle for 1000 in current.  I'd prefer
20k to disabled!

> Raise GCInspector alerts to WARN
> --------------------------------
>                 Key: CASSANDRA-8907
>                 URL:
>             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 (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 (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

View raw message