cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2941) Expose number of rpc timeouts for individual hosts metric via jmx
Date Tue, 26 Jul 2011 14:49:09 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071131#comment-13071131
] 

Jonathan Ellis commented on CASSANDRA-2941:
-------------------------------------------

- does not apply to 0.8 for me
- i don't see anything to prevent dropping timeouts b/c of race in timeoutreporter.apply.
 (using NBHM + replace would fix this)
- if you did the recentTimeouts create first, then the timeouts put, you wouldn't have to
special case recent == null later

> Expose number of rpc timeouts for individual hosts metric via jmx 
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-2941
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2941
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Melvin Wang
>            Assignee: Melvin Wang
>            Priority: Minor
>         Attachments: twttr-cassandra-0.8-counts-resync-timeouts-metric.diff
>
>
> We have a total number timeouts for each node. It's better for monitoring to break down
this total number into number of timeouts per host that this node tried to connect to.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message