[
https://issues.apache.org/jira/browse/HADOOP-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-3837:
-------------------------------------
Fix Version/s: 0.19.0
0.18.0
Release Note: Streaming tasks adhere to task timeout value specified in
the job configuration.
Hadoop Flags: [Incompatible change]
Status: Patch Available (was: Open)
I would like to apply this patch to trunk as well as 0.18.
> 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
> Fix For: 0.18.0, 0.19.0
>
> Attachments: 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.
