Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F3865200C45 for ; Tue, 28 Mar 2017 21:10:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id F21A6160B9B; Tue, 28 Mar 2017 19:10:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 44120160B6B for ; Tue, 28 Mar 2017 21:10:45 +0200 (CEST) Received: (qmail 52795 invoked by uid 500); 28 Mar 2017 19:10:44 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 52784 invoked by uid 99); 28 Mar 2017 19:10:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Mar 2017 19:10:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 076FA1A01AC for ; Tue, 28 Mar 2017 19:10:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Ks0YgngRF_OE for ; Tue, 28 Mar 2017 19:10:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id A0B1A5F2FE for ; Tue, 28 Mar 2017 19:10:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DAE2FE0534 for ; Tue, 28 Mar 2017 19:10:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 90FED25CE8 for ; Tue, 28 Mar 2017 19:10:41 +0000 (UTC) Date: Tue, 28 Mar 2017 19:10:41 +0000 (UTC) From: "Eric Yablonowitz (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-12848) Nodetool proxyhistograms/cfhistograms still report latency as flat result MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Mar 2017 19:10:46 -0000 [ 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)