hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3837) hadop streaming does not use progress reporting to detect hung tasks
Date Fri, 01 Aug 2008 22:55:31 GMT

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

Doug Cutting commented on HADOOP-3837:

> I will commit this to trunk and 0.18 by the end of this week. 

The week is almost up...

> 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.

View raw message