[
https://issues.apache.org/jira/browse/CASSANDRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073325#comment-13073325
]
Melvin Wang commented on CASSANDRA-2941:
----------------------------------------
patch are old, need to rebase. i'll do it.
timeoutreporter.apply is only called in one thread, right? In expireMap, a
timerTask will be created to monitor the cache, yes/no ?
If the previous is true, the reason for me to do it this way is that I only do
'write' operation to the hashmap in one thread so that we will not corrupt the
data structure. Although get**** is called from multi threaded, only 'read'
operations of hashmap is performed so we don't need 'lock' here. I think this
is the reason I try not to create an atomicLong and insert into hashmap.
> 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
>
> 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
