You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2010/10/25 04:38:20 UTC

[jira] Created: (CASSANDRA-1660) Log GC/tpstats info when messages are dropped.

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
    Affects Versions: 0.7.0
            Reporter: Brandon Williams
            Priority: Minor
             Fix For: 0.7.1


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.

[jira] Commented: (CASSANDRA-1660) Log GC/tpstats info when messages are dropped.

Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926328#action_12926328 ] 

Brandon Williams commented on CASSANDRA-1660:
---------------------------------------------

+1

> 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
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6.7, 0.7.0
>
>         Attachments: 1660.txt
>
>
> 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.

[jira] Updated: (CASSANDRA-1660) Log GC/tpstats info when messages are dropped.

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ 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.

[jira] Updated: (CASSANDRA-1660) Log GC/tpstats info when messages are dropped.

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Attachment: 1660.txt

(patch is against 0.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
>
>         Attachments: 1660.txt
>
>
> 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.

[jira] Updated: (CASSANDRA-1660) Log GC/tpstats info when messages are dropped.

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Affects Version/s:     (was: 0.7.0)
        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
>            Reporter: Brandon Williams
>            Priority: Minor
>             Fix For: 0.6.7, 0.7.1
>
>
> 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.