[ http://issues.apache.org/jira/browse/HADOOP-491?page=comments#action_12431391 ] Doug Cutting commented on HADOOP-491: -------------------------------------
There already is an API for tasks to say they're alive: Reporter.setStatus() and progress(). This may not be well documented, so perhaps this is a documentation bug? > there should be a protocol for a map or reduce task to tell the jobtracker > its alive > ------------------------------------------------------------------------------------ > > Key: HADOOP-491 > URL: http://issues.apache.org/jira/browse/HADOOP-491 > Project: Hadoop > Issue Type: New Feature > Components: mapred > Reporter: arkady borkovsky > > Currently, the jobtracker relies on task to write something to the output to > know the tasks are still alive. > There is a 600 seconds timeout preset. > Some tasks spend longer that 600 seconds without any output while being > perfectly healthy. > It would be good to have an API for a task to explicitly tell the jobtracker > it is alive. > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
