[
https://issues.apache.org/jira/browse/MAPREDUCE-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207300#comment-13207300
]
Hadoop QA commented on MAPREDUCE-3846:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12514400/MAPREDUCE-3846-20120213.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 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 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any 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/1847//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1847//console
This message is automatically generated.
> Restarted+Recovered AM hangs in some corner cases
> -------------------------------------------------
>
> Key: MAPREDUCE-3846
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3846
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Critical
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3846-20120210.txt,
> MAPREDUCE-3846-20120210.txt, MAPREDUCE-3846-20120213.txt
>
>
> [~karams] found this while testing AM restart/recovery feature. After the
> first generation AM crashes (manually killed by kill -9), the second
> generation AM starts, but hangs after a while.
--
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
