You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2014/04/03 00:25:15 UTC
[jira] [Commented] (CASSANDRA-6920) LatencyMetrics can return
infinity
[ https://issues.apache.org/jira/browse/CASSANDRA-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958258#comment-13958258 ]
Nick Bailey commented on CASSANDRA-6920:
----------------------------------------
FWIW, I said "potential" fix because I didn't really know if there were performance concerns adding that synchronized block on a method we call for every read/write that comes in to the system.
Just wanted to mention that here in case there are concerns.
> 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)