[
https://issues.apache.org/jira/browse/HADOOP-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624673#action_12624673
]
Hudson commented on HADOOP-3837:
--------------------------------
Integrated in Hadoop-trunk #581 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> 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.
