[
https://issues.apache.org/jira/browse/CASSANDRA-12848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379363#comment-16379363
]
Chris Lohfink commented on CASSANDRA-12848:
-------------------------------------------
I think this can be reported as not a problem, just a artifact of using
histograms to store metrics vs a sampling reservoir
> Nodetool proxyhistograms/cfhistograms still report latency as flat result
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-12848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12848
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Nutchanon Leelapornudom
> Priority: Major
> Labels: metrics
> Attachments: clientrequest-latency.png, image001.png
>
>
> Even patched in CASSANDRA-11752, nodetool
> proxyhistograms/cfhistograms(2.2)/tablehistograms(3.0,3.x) still report
> read/write latency as flat result. That cause Cassandra metric
> org.apache.cassandra.metrics.ClientRequest.Read/Write.Latency.xxpercentile
> report incorrect pattern.
> I have attached the result which I tested on cassandra 3.0.9. It indicate
> read latency as flat line whereas read count has a movement normally.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
