[
https://issues.apache.org/jira/browse/CASSANDRA-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959385#comment-13959385
]
Benedict commented on CASSANDRA-6920:
-------------------------------------
Well, I'm quite comfortable leaving the read operation synchronized - although
it will still be nonsense if there's more than one caller, it will be
marginally less nonsense. So long as we're only paying a penalty on read of the
metric and not on every database operation.
> LatencyMetrics can return infinity
> -----------------------------------
>
> Key: CASSANDRA-6920
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6920
> Project: Cassandra
> Issue Type: Bug
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Fix For: 1.2.17, 2.0.7, 2.1 beta2
>
> Attachments: 6920-cassandra-1.2.patch, 6920-cassandra-2.0.patch,
> 6920-infinity-metrics.patch
>
>
> There is a race condition when updating the recentLatency metrics exposed
> from LatencyMetrics.
> Attaching a patch with a test that exposes the issue and a potential fix.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
