[ https://issues.apache.org/jira/browse/MAPREDUCE-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222722#comment-13222722 ]
Hadoop QA commented on MAPREDUCE-3034: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12517129/MAPREDUCE-3034-20120305.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 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/2004//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2004//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-nodemanager.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2004//console This message is automatically generated. > NM should act on a REBOOT command from RM > ----------------------------------------- > > Key: MAPREDUCE-3034 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3034 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager > Affects Versions: 0.23.0 > Reporter: Vinod Kumar Vavilapalli > Assignee: Devaraj K > Priority: Critical > Fix For: 0.23.2 > > Attachments: MAPREDUCE-3034-1.patch, MAPREDUCE-3034-2.patch, > MAPREDUCE-3034-20120305.txt, MAPREDUCE-3034-3.patch, MAPREDUCE-3034-4.patch, > MAPREDUCE-3034-5.patch, MAPREDUCE-3034.patch, MR-3034.txt > > > RM sends a reboot command to NM in some cases, like when it gets lost and > rejoins back. In such a case, NM should act on the command and > reboot/reinitalize itself. > This is akin to TT reinitialize on order from JT. We will need to shutdown > all the services properly and reinitialize - this should automatically take > care of killing of containers, cleaning up local temporary files etc. -- 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