You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2008/10/22 00:40:44 UTC
[jira] Updated: (HADOOP-3837) hadop streaming does not use progress
reporting to detect hung tasks
[ https://issues.apache.org/jira/browse/HADOOP-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-3837:
------------------------------------
Release Note: Changed streaming tasks to adhere to task timeout value specified in the job configuration. (was: Streaming tasks adhere to task timeout value specified in the job configuration.)
> hadop streaming does not use progress reporting to detect hung tasks
> --------------------------------------------------------------------
>
> Key: HADOOP-3837
> URL: https://issues.apache.org/jira/browse/HADOOP-3837
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/streaming
> Affects Versions: 0.17.0
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.18.0, 0.19.0
>
> Attachments: streamTimeout.patch, streamTimeout.patch
>
>
> Hadoop streaming (StreamJob.java) sets mapred.task.timeout to 0. This effectively means that if tasks hang (either due to bad user code or machine related issue), these tasks never encounters a timeout. This causes the entire job to hang.
> I propose that hadoop streaming not set the timeout to 0. By default, the settings in hadoop-default.xml should be effective for streaming jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.