Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sun, 5 Feb 2012 00:27:53 +0000 (UTC)
From: "Arun C Murthy (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1474057930.12178.1328401673634.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <652699180.2870.1327710621239.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3747) Memory Total is not refreshed
 until an app is launched
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy updated MAPREDUCE-3747:
-------------------------------------

    Attachment: MAPREDUCE-3747.patch

Fixed.
                
> Memory Total is not refreshed until an app is launched
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-3747
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3747
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Ramya Sunil
>            Assignee: Arun C Murthy
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3747.patch, MAPREDUCE-3747.patch, MAPREDUCE-3747.patch, MAPREDUCE-3747.patch, MAPREDUCE-3747.patch
>
>
> Memory Total on the RM UI is not refreshed until an application is launched. This is a problem when the cluster is started for the first time or when there are any lost/decommissioned NMs.
> When the cluster is started for the first time, Active Nodes is > 0 but the Memory Total=0. Also when there are any lost/decommissioned nodes, Memory Total has wrong value.
> This is a useful tool for cluster admins and has to be updated correctly without having the need to submit an app each time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira