[jira] [Updated] (MAPREDUCE-4937) MR AM handles an oversized split metainfo file poorly

["Eric Payne (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Payne updated MAPREDUCE-4937:
----------------------------------

    Target Version/s: trunk
              Status: Patch Available  (was: Open)

Reproduced by setting mapreduce.jobtracker.split.metainfo.maxsize to something small:
 $HADOOP_PREFIX/bin/hadoop jar ~/run/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-$HADOOP_VERSION.jar wordcount -Dmapreduce.jobtracker.split.metainfo.maxsize=10 InputDir OutputDir/O1

> 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: 0.23.5, 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Eric Payne
>
> 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)