[
https://issues.apache.org/jira/browse/CASSANDRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078397#comment-13078397
]
Jonathan Ellis commented on CASSANDRA-2941:
-------------------------------------------
bq. Although get**** is called from multi threaded, only 'read' operations of
hashmap is performed so we don't need 'lock' here.
Actually, we still need to establish a happens-before for the read, or we have
no guarantees that the JMX thread will ever see the updates made by the timeout
reporter. So we could either use a Map of AtomicLong or a ConcurrentMap of
Long.
> 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
