[
https://issues.apache.org/jira/browse/CASSANDRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078469#comment-13078469
]
Melvin Wang commented on CASSANDRA-2941:
----------------------------------------
I am not clear why we have no guarantees that the JMX thread will ever see the
updates made by the timeout reporter. The current structure is that, if there
is a timeout happened, apply() will be called for it and if this is the first
time for a certain IP address, an atomicLong will be created for it. Since this
is the first time for this IP address to time out, it is natural not to see its
updates before. From then on, it will get updated whenever JMX threads call
getRecent***(). Maybe I miss something here?
> 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: c2941.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
