Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 2 Jun 2011 03:17:47 +0000 (UTC)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <694716458.61788.1306984667688.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <40797085.17439.1304397363120.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-2469) Task counters should also report
 the total heap usage of the task
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Amar Kamat updated MAPREDUCE-2469:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.0
     Release Note: Task attempt's total heap usage gets recorded and published via counters as COMMITTED_HEAP_BYTES.
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I just committed the latest patch to trunk. Thanks Ravi, Santosh and Owen!

> Task counters should also report the total heap usage of the task
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-2469
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2469
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: task
>    Affects Versions: 0.23.0
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>              Labels: mapreduce
>             Fix For: 0.23.0
>
>         Attachments: 2469.v0.1.patch, mapreduce-2469-v1.1.patch, mapreduce-2469-v1.2.patch, mapreduce-2469-v1.3.patch, mapreduce-2469-v1.4.patch
>
>
> Currently, the task counters report VSS and RSS usage of the task. The task counter should also report the total heap usage of the task also. The task might be configured with a max heap size of M but the task's total heap usage might only be H, where H < M. In such a case, knowing only M doesn't provide a complete picture of the task's memory usage.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira