cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10975) Histogram buckets exposed in jmx are sorted by count
Date Thu, 07 Jan 2016 14:33:39 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

T Jake Luciani updated CASSANDRA-10975:
---------------------------------------
    Fix Version/s: 2.2.5

> Histogram buckets exposed in jmx are sorted by count
> ----------------------------------------------------
>
>                 Key: CASSANDRA-10975
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10975
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Observability
>            Reporter: Chris Lohfink
>             Fix For: 2.2.5, 3.0.3, 3.2
>
>         Attachments: 10975-2.2.patch
>
>
> The estimated histogram snapshot lets its parent provide the getValues implementation
which sorts the bucket array:
> https://github.com/dropwizard/metrics/blob/3.1-maintenance/metrics-core/src/main/java/com/codahale/metrics/UniformSnapshot.java#L25
> making it hard to determine what count belonged to what bucket. Along with removal of
the pre 2.2 deprecated metrics this makes it nearly impossible to track latencies over time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message