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 2CE6D200C1D for ; Thu, 2 Feb 2017 00:12:56 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2B7C8160B63; Wed, 1 Feb 2017 23:12:56 +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 76263160B46 for ; Thu, 2 Feb 2017 00:12:55 +0100 (CET) Received: (qmail 90151 invoked by uid 500); 1 Feb 2017 23:12:54 -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 90142 invoked by uid 99); 1 Feb 2017 23:12:54 -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, 01 Feb 2017 23:12:54 +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 439FEC0115 for ; Wed, 1 Feb 2017 23:12:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id vOaNF4w2ZmgP for ; Wed, 1 Feb 2017 23:12:53 +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 A7BC05F19B for ; Wed, 1 Feb 2017 23:12:52 +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 BF3E0E01D8 for ; Wed, 1 Feb 2017 23:12:51 +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 7ADEC2527C for ; Wed, 1 Feb 2017 23:12:51 +0000 (UTC) Date: Wed, 1 Feb 2017 23:12:51 +0000 (UTC) From: "Qin Liu (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 01 Feb 2017 23:12:56 -0000 Qin Liu created AMBARI-19829: -------------------------------- Summary: Several HDFS/YARN widgets on Heatmaps show N/A Key: AMBARI-19829 URL: https://issues.apache.org/jira/browse/AMBARI-19829 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.2 Reporter: Qin Liu Assignee: Qin Liu Fix For: trunk The following HDFS/YARN widgets on Heatmaps show N/A: 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O Utilization, and DataNode Process Network I/O Utilization 2. YANR - Container Failures The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do not show up on Ambari" which introduced rate metrics and applied rate metrics to several HBASE/HDFS/YARN widgets on Summary pages as well as Heatmap pages. Rate metrics work fine on Summary pages but they don't work on Heatmap pages because current Heatmap design can only show point-in-time metrics and rate metrics need a time range. -- This message was sent by Atlassian JIRA (v6.3.15#6346)