cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yablonowitz (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12848) Nodetool proxyhistograms/cfhistograms still report latency as flat result
Date Tue, 28 Mar 2017 19:10:41 GMT

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

Eric Yablonowitz updated CASSANDRA-12848:
-----------------------------------------
    Attachment: clientrequest-latency.png

We saw exactly the same doing an upgrade from 2.1.15 to 3.0.12.  Attachment shows a graph
of `org.apache.cassandra.metrics:type=ClientRequest,scope=*,name=Latency` 50thPercentile that
spans the upgrade.

The 2.1 part of the graph shows expected variability whereas the latter is unnaturally flat.

> 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
>              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
(v6.3.15#6346)

Mime
View raw message