[ https://issues.apache.org/jira/browse/MAPREDUCE-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488431#comment-13488431 ]
Hadoop QA commented on MAPREDUCE-4729: -------------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12551662/MAPREDUCE-4729-20121031.txt 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 1 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. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2974//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2974//console This message is automatically generated. > job history UI not showing all job attempts > ------------------------------------------- > > Key: MAPREDUCE-4729 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4729 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver > Affects Versions: 0.23.3 > Reporter: Thomas Graves > Assignee: Vinod Kumar Vavilapalli > Attachments: MAPREDUCE-4729-20121031.txt > > > We are seeing a case where a job runs but the AM is running out of memory in > the first 3 attempts. The job eventually finishes on the 4th attempt. When > you go to the job history UI for that job, it only shows the last attempt. > This is bad since we want to see why the first 3 attempts failed. > The RM web ui shows all 4 attempts. > Also I tested this locally by running "kill" on the app master and in that > case the history server UI does show all attempts. -- 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