hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (MAPREDUCE-421) mapred pipes might return exit code 0 even when failing
Date Thu, 27 Aug 2009 22:06:59 GMT

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

Owen O'Malley resolved MAPREDUCE-421.
-------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

I realized that this was difficult to test.

I just committed this. Thanks, Christian!



> mapred pipes might return exit code 0 even when failing
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-421
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-421
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: pipes
>            Reporter: Christian Kunz
>            Assignee: Christian Kunz
>             Fix For: 0.20.1
>
>         Attachments: MAPREDUCE-421.patch
>
>
> up to  hadoop 0.18.3 org.apache.hadoop.mapred.JobShell ensured that 'hadoop jar' returns
non-zero exit code when the job fails.
> This is no longer true after moving this to org.apache.hadoop.util.RunJar.
> Pipes jobs submitted through cli never returned proper exit code.
> The main methods in org.apache.hadoop.util.RunJar. and org.apache.hadoop.mapred.pipes.Submitter
should be modified to return an exit code similar to how org.apache.hadoop.mapred.JobShell
did it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message