Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 24 Oct 2011 20:38:33 +0000 (UTC)
From: "Mahadev konar (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <579891820.10365.1319488713454.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1740950529.29312.1313087307667.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-2821) [MR-279] Missing fields in job
 summary logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mahadev konar updated MAPREDUCE-2821:
-------------------------------------

    Status: Patch Available  (was: Open)
    
> [MR-279] Missing fields in job summary logs 
> --------------------------------------------
>
>                 Key: MAPREDUCE-2821
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2821
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Ramya Sunil
>            Assignee: Mahadev konar
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2821.patch, MAPREDUCE-2821.patch, MAPREDUCE-2821.patch
>
>
> The following fields are missing in the job summary logs in mrv2:
> - numSlotsPerMap
> - numSlotsPerReduce
> - clusterCapacity (Earlier known as clusterMapCapacity and clusterReduceCapacity in 0.20.x)
> The first two fields are important to know if the job was a High RAM job or not and the last field is important to know the total available resource in the cluster during job execution.

--
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