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 B41D0200CDD for ; Mon, 7 Aug 2017 23:01:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B2DB116618D; Mon, 7 Aug 2017 21:01:11 +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 041FD16618B for ; Mon, 7 Aug 2017 23:01:10 +0200 (CEST) Received: (qmail 49772 invoked by uid 500); 7 Aug 2017 21:01:10 -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 49763 invoked by uid 99); 7 Aug 2017 21:01:10 -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; Mon, 07 Aug 2017 21:01:10 +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 C88331A06C4 for ; Mon, 7 Aug 2017 21:01:09 +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 ZOFm4D9MOXYV for ; Mon, 7 Aug 2017 21:01:05 +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 2FD6D61B57 for ; Mon, 7 Aug 2017 21:01:03 +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 2F8FEE0E4A for ; Mon, 7 Aug 2017 21:01:02 +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 00729241A1 for ; Mon, 7 Aug 2017 21:01:01 +0000 (UTC) Date: Mon, 7 Aug 2017 21:01:00 +0000 (UTC) From: "Siddharth Wagle (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 07 Aug 2017 21:01:11 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117259#comment-16117259 ] Siddharth Wagle commented on AMBARI-21664: ------------------------------------------ ---------------------------------------------------------------------- Ran 274 tests in 6.821s OK ---------------------------------------------------------------------- Total run:1162 Total errors:0 Total failures:0 OK > HDFS namenode rpc and connection load metrics are not showing > ------------------------------------------------------------- > > Key: AMBARI-21664 > URL: https://issues.apache.org/jira/browse/AMBARI-21664 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Affects Versions: 2.5.2 > Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2 > Reporter: Eric Yang > Assignee: Siddharth Wagle > Fix For: 2.5.2 > > Attachments: AMBARI-21664.patch > > > After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two metrics widget don't show the right results. > Namenode RPC and Namenode Connection Load graph don't show any data. This might be caused by different implementation to fetch metrics data for those two graphs in IOP. Check if there is a way to bridge the gap by updating widget information or document this and ask user to remove the widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)