You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/01/11 22:26:12 UTC
[jira] [Created] (MAPREDUCE-4937) MR AM handles an oversized split
metainfo file poorly
Jason Lowe created MAPREDUCE-4937:
-------------------------------------
Summary: 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
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 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