[
https://issues.apache.org/jira/browse/MAPREDUCE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106006#comment-13106006
]
Hadoop QA commented on MAPREDUCE-3006:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12494783/MAPREDUCE-3006-20110916.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 15 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/760//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/760//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/760//console
This message is automatically generated.
> 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
