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 Sun, 31 Jul 2011 21:03:09 GMT

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

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

bq. timeoutreporter.apply is only called in one thread, right?

you're right, that should be fine.

bq. rebased my patch.

What did you rebase against?  There have been no commits in the meantime but it does not apply
to 0.8 head.

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