hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4937) MR AM handles an oversized split metainfo file poorly
Date Wed, 16 Apr 2014 16:56:25 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971646#comment-13971646

Hadoop QA commented on MAPREDUCE-4937:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  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}.  There were no new javadoc 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/4526//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4526//console

This message is automatically generated.

> 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
>         Attachments: 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

View raw message