cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1660) Log GC/tpstats info when messages are dropped.
Date Thu, 28 Oct 2010 15:10:19 GMT


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

View raw message