Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <863615835.74561267725447299.JavaMail.jira@brutus.apache.org>
Date: Thu, 4 Mar 2010 17:57:27 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Updated: (CASSANDRA-813) add some kind of logging of GC
 activity
In-Reply-To: <1312567563.409121266640167914.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.