Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26E5E10FDB for ; Tue, 26 Nov 2013 01:23:41 +0000 (UTC) Received: (qmail 2590 invoked by uid 500); 26 Nov 2013 01:23:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 2525 invoked by uid 500); 26 Nov 2013 01:23:40 -0000 Mailing-List: contact dev-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 dev@ambari.apache.org Received: (qmail 2370 invoked by uid 99); 26 Nov 2013 01:23:40 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 01:23:40 +0000 Date: Tue, 26 Nov 2013 01:23:40 +0000 (UTC) From: "Xi Wang (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-3878) ResourceManager Heap metrics is not correct on Ambari console MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832165#comment-13832165 ] Xi Wang commented on AMBARI-3878: --------------------------------- Tested end to end. Worked fine. > ResourceManager Heap metrics is not correct on Ambari console > ------------------------------------------------------------- > > Key: AMBARI-3878 > URL: https://issues.apache.org/jira/browse/AMBARI-3878 > Project: Ambari > Issue Type: Bug > Components: client > Affects Versions: 1.4.2 > Reporter: Xi Wang > Assignee: Xi Wang > Fix For: 1.4.2 > > Attachments: AMBARI-3878.patch > > > PROBLEM: The ResourceManager Heap metrics on Ambari web console doesn't show the correct value, not only the current heap usage doesn't reflect the correct usage, but also the total heap size doesn't match what we configure for the ResourceManager Heap size, even the total heap size number is changing constantly. -- This message was sent by Atlassian JIRA (v6.1#6144)