hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Kunz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6030) hadoop jar and hadoop/mapred pipes might return exit code 0 even when failing
Date Fri, 19 Jun 2009 22:30:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722067#action_12722067

Christian Kunz commented on HADOOP-6030:

As Qi's comment indicates, the statement in the description should be changed.

'hadoop jar' will return correct exit code depending on the handling of uncaught exceptions.
If the default handler has as consequence a non-zero exit code (seems to be the case, but
is this fact actually documented somewhere?), then no change is needed.

'mapred pipes' still needs modifications to return non-zero exit code for improper submission.

> hadoop jar and hadoop/mapred pipes might return exit code 0 even when failing
> -----------------------------------------------------------------------------
>                 Key: HADOOP-6030
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6030
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Christian Kunz
> 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.

View raw message