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 7B9B9200C09 for ; Wed, 25 Jan 2017 22:01:34 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 78564160B4E; Wed, 25 Jan 2017 21:01:34 +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 C186D160B3D for ; Wed, 25 Jan 2017 22:01:33 +0100 (CET) Received: (qmail 85629 invoked by uid 500); 25 Jan 2017 21:01:33 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 85619 invoked by uid 99); 25 Jan 2017 21:01:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2017 21:01:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 996ECC0B3C for ; Wed, 25 Jan 2017 21:01:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.003 X-Spam-Level: X-Spam-Status: No, score=0.003 tagged_above=-999 required=6.31 tests=[KAM_BADIPHTTP=2, KAM_LAZY_DOMAIN_SECURITY=1, NORMAL_HTTP_TO_IP=0.001, RP_MATCHES_RCVD=-2.999, WEIRD_PORT=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 3Z-6phHsS2GF for ; Wed, 25 Jan 2017 21:01:30 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 8EA4B5F3BF for ; Wed, 25 Jan 2017 21:01:30 +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 A6C22E0146 for ; Wed, 25 Jan 2017 21:01:26 +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 6502925289 for ; Wed, 25 Jan 2017 21:01:26 +0000 (UTC) Date: Wed, 25 Jan 2017 21:01:26 +0000 (UTC) From: "Vivek Ratnavel Subramanian (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-19717) HDFS TopN Operations by User graph showing wrong data in grafana MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 25 Jan 2017 21:01:34 -0000 Vivek Ratnavel Subramanian created AMBARI-19717: --------------------------------------------------- Summary: HDFS TopN Operations by User graph showing wrong data in grafana Key: AMBARI-19717 URL: https://issues.apache.org/jira/browse/AMBARI-19717 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 The Operations by User (1min & 5min sliding window) graphs in Grafana HDFS TopN dashboard is showing wrong data. The total count range is much lesser than the ranges of all the other graphs. I have a live cluster available at http://104.196.90.100:3000/dashboard/db/hdfs-topn -- This message was sent by Atlassian JIRA (v6.3.4#6332)