[ https://issues.apache.org/jira/browse/MAPREDUCE-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974465#comment-13974465 ]
Hudson commented on MAPREDUCE-4937: ----------------------------------- SUCCESS: Integrated in Hadoop-trunk-Commit #5538 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5538/]) MAPREDUCE-4937. MR AM handles an oversized split metainfo file poorly. Contributed by Eric Payne (jlowe: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1588559) * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/job/event/JobEventType.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/job/impl/JobImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TestJobImpl.java > MR AM handles an oversized split metainfo file poorly > ----------------------------------------------------- > > Key: MAPREDUCE-4937 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4937 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mr-am > Affects Versions: 2.0.2-alpha, 0.23.5 > Reporter: Jason Lowe > Assignee: Eric Payne > Fix For: 3.0.0, 2.5.0 > > Attachments: MAPREDUCE-4937.MRAMHandlOversizeSplits.txt, > MAPREDUCE-4937.MRAMHandlOversizeSplits.txt, > MAPREDUCE-4937.MRAMHandlOversizeSplits.txt > > > When an job runs with a split metainfo file that's larger than it has been > configured to handle then it just crashes. This leaves the user with a > less-than-ideal debug session since there are no useful diagnostic messages > sent to the client for this failure. In addition it crashes before > registering/unregistering with the RM and crashes without generating history, > so the proxy URL is not very useful and there's no archived configuration to > check to see what setting the AM was using when it encountered the error. > The AM should handle this error case more gracefully and treat the failure as > it does any other failed job, with a proper unregistration from the RM and > with history. -- This message was sent by Atlassian JIRA (v6.2#6252)