[jira] Commented: (HADOOP-491) streaming jobs should allow programs that don't do any IO for a long time

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-491) streaming jobs should allow programs that don't do any IO for a long time

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462099 ]

Owen O'Malley commented on HADOOP-491:
--------------------------------------

I think the right way to address this is to support timeouts of "0" that mean there should be no task timeouts. The default in streaming can be set to 0, since it is impossible for the streaming process to call reporter.progress().

> streaming jobs should allow programs that don't do any IO for a long time
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-491
>                 URL: https://issues.apache.org/jira/browse/HADOOP-491
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/streaming
>            Reporter: arkady borkovsky
>         Assigned To: Sanjay Dahiya
>
> The jobtracker relies on task to send heartbeats  to know the tasks are still alive.
> There is a 600 seconds timeout preset.
> hadoop streaming also uses input to or output from the program it spawns to indicate progress, sending appropriate heartbeats.
> Some spawned programs spend longer that 600 seconds without any output while being perfectly healthy.
> It would be good to enhance the interface between hadoop streaming and the programs it spawns to track a healthy program in the absense of output.
> There are certain dangers with this protocol: e.g. a task can run a separate thread that does nothing but send "i'm alive" message.   This would be a user bug to abuse the API in such way.  

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