hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2057) streaming should optionally treat a non-zero exit status of a child process as a failed task
Date Mon, 10 Mar 2008 16:55:51 GMT

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

Tom White updated HADOOP-2057:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I've just committed this. Thanks Rick!

I haven't included the change to include the new property in hadoop-default.xml, since core
shouldn't depend on contrib code.

> streaming should optionally treat a non-zero exit status of a child process as a failed
> --------------------------------------------------------------------------------------------
>                 Key: HADOOP-2057
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2057
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/streaming
>    Affects Versions: 0.14.0, 0.14.1, 0.14.2, 0.14.3, 0.14.4, 0.15.0, 0.15.1, 0.15.2,
0.15.3, 0.16.0
>            Reporter: Rick Cox
>            Assignee: Rick Cox
>             Fix For: 0.17.0
>         Attachments: exit-status-2057-0.16.patch
> The exit status of the external processes spawned by streaming tasks is currently logged,
but not used to indicate success or failure of the task. While this is reasonable for some
UNIX tools (e.g. grep), many programs will indicate failure by a non-zero exit status. (Also,
even for custom programs, intentionally indicating the failure of a streaming task is currently
rather tricky.)
> This could be supported by adding a new job-configuration setting, 'stream.non.zero.exit.is.failure'.
If true, a non-zero exit status of a child process would throw an exception in the PipeMapRed,
causing task failure. The current behavior would be preserved by using a default setting of
> This would allow streaming tasks to easily indicate failure, even if all input has already
been consumed.

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

View raw message