[ https://issues.apache.org/jira/browse/MAPREDUCE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542561#comment-13542561 ]
Hadoop QA commented on MAPREDUCE-4832: -------------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12562975/MAPREDUCE-4832.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 7 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3185//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3185//console This message is automatically generated. > MR AM can get in a split brain situation > ---------------------------------------- > > Key: MAPREDUCE-4832 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4832 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster > Affects Versions: 2.0.2-alpha, 0.23.5 > Reporter: Robert Joseph Evans > Assignee: Jason Lowe > Priority: Critical > Attachments: MAPREDUCE-4832.patch > > > It is possible for a networking issue to happen where the RM thinks an AM has > gone down and launches a replacement, but the previous AM is still up and > running. If the previous AM does not need any more resources from the RM it > could try to commit either tasks or jobs. This could cause lots of problems > where the second AM finishes and tries to commit too. This could result in > data corruption. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira