hadoop-common-dev mailing list archives

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

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

Qi Liu commented on HADOOP-6030:
--------------------------------

Can we use Thread.setUncaughtExceptionHandler() to resolve this?

> 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.


Mime
View raw message