[
https://issues.apache.org/jira/browse/CASSANDRA-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765540#comment-13765540
]
Yuki Morishita commented on CASSANDRA-5947:
-------------------------------------------
With this update, I see o.a.c.metrics.ColumnFamily and ThreadPools are unquoted
and all others are quoted.
This is because above those metrics build their own JMX object name instead of
auto generating from coda metrics name.
We can force JMX name as before, and I think we should to avoid confusion.
> Sampling bug in metrics-core-2.0.3.jar used by Cassandra
> --------------------------------------------------------
>
> Key: CASSANDRA-5947
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5947
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: J.B. Langston
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.2.10, 2.0.1
>
> Attachments: Screen Shot 2013-09-10 at 2.23.11 PM.png
>
>
> There is a sampling bug in the version of the metrics library we're using in
> Cassandra. See https://github.com/codahale/metrics/issues/421.
> ExponentiallyDecayingSample is used by the Timer's histogram that is used in
> stress tool, and according to [~brandon.williams] it is also in a few other
> places like the dynamic snitch. The statistical theory involved in this bug
> goes over my head so i'm not sure if this would bug would meaningfully affect
> its usage by Cassandra. One of the comments on the bug mentions that it
> affects slow sampling rates (10 samples/min was the example given). We're
> currently distributing metrics-core-2.0.3.jar and according to the release
> nodes, this bug is fixed in 2.1.3:
> http://metrics.codahale.com/about/release-notes/#v2-1-3-aug-06-2012
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
