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] Resolved: (HADOOP-540) Streaming should send keep-alive signals to Reporter
Date Mon, 18 Sep 2006 23:07:23 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-540?page=all ]

Doug Cutting resolved HADOOP-540.
---------------------------------

    Fix Version/s: 0.7.0
       Resolution: Fixed

This should have been fixed by HADOOP-542.

> Streaming should send keep-alive signals to Reporter
> ----------------------------------------------------
>
>                 Key: HADOOP-540
>                 URL: http://issues.apache.org/jira/browse/HADOOP-540
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/streaming
>            Reporter: Michel Tourn
>             Fix For: 0.7.0
>
>
> The goal is to avoid the 10-minutes Task timeout with certain usages of hadoopStreaming.
> This proposal does not introduce an artificial keep-alive heartbeat: 
> it still requires the external Application to have activity.
> Streaming should set Reporter status in more places:
> 1. output to side-effect files should (periodically) set reporter status.
> 2. Application's stderr data should (periodically) set reporter status.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message