Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 16 Sep 2011 11:16:09 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <228709630.34327.1316171769111.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <579183339.26215.1315998550250.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3006) MapReduce AM exits prematurely
 before completely writing and closing the JobHistory file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli updated MAPREDUCE-3006:
-----------------------------------------------

    Status: Patch Available  (was: Open)

> MapReduce AM exits prematurely before completely writing and closing the JobHistory file
> ----------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3006
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3006
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-3006-20110915.txt, MAPREDUCE-3006-20110916.txt
>
>
> [~Karams] was executing a sleep job with 100,000 tasks on a 350 node cluster to test MR AM's scalability and ran into this. The job ran successfully but the history was not available.
> I debugged around and figured that the job is finishing prematurely before the JobHistory is written. In most of the cases, we don't see this bug as we have a 5 seconds sleep in AM towards the end.

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