hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2057) streaming should optionally treat a non-zero exit status of a child process as a failed task
Date Thu, 06 Mar 2008 04:40:58 GMT

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

Amareshwari Sriramadasu commented on HADOOP-2057:

Sorry for responding late. 
Code looks good. Can you submit patch again updated with the trunk?
And make it Patch available for hudson to test it? 

> 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.15.0
>            Reporter: Rick Cox
>         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