cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6920) LatencyMetrics can return infinity
Date Thu, 03 Apr 2014 22:45:17 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959366#comment-13959366
] 

Nick Bailey commented on CASSANDRA-6920:
----------------------------------------

Thats true enough, it presents potential problems if there are multiple readers of the metric
(the possibility of one reader always hitting the race and getting 0), but that's one of the
problems with using this metric anyway.

Like I said, since this metric is deprecated I'm not particularly concerned now that I know
where the infinity values are coming from and I can work around them.

> 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)

Mime
View raw message