Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <14386024.122141288278619595.JavaMail.jira@thor>
Date: Thu, 28 Oct 2010 11:10:19 -0400 (EDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1660) Log GC/tpstats info when messages
 are dropped.
In-Reply-To: <27981390.52711287974300131.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1660:
--------------------------------------

      Component/s: Core
    Fix Version/s: 0.6.7

> Log GC/tpstats info when messages are dropped.
> ----------------------------------------------
>
>                 Key: CASSANDRA-1660
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1660
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Priority: Minor
>             Fix For: 0.6.7, 0.7.0
>
>
> In CASSANDRA-685 we began dropping messages past the rpc timeout (and in CASSANDRA-1284 began printing a summary of these.)  The next logical step when this is encountered is to find out why they were dropped, and that usually involves looking at tpstats.  Since the GCInspector does this, I propose a) changing the CASSANDRA-1284 interval to 10s, and b) having it ask the GCInspector to print its usual summary, which will include tpstats.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.