[ http://issues.apache.org/jira/browse/HADOOP-133?page=comments#action_12374423 ]
Owen O'Malley commented on HADOOP-133: -------------------------------------- Ok, I can see wanting to try gently first and then pull out the exit sledgehammer if it doesn't work. Checking back with the taskTracker once a second seems too frequent. I'd also propose changing the ping message to return a boolean that means the task should exit, so that IOException can mean that there was a communication error. If there is a communication error, it would make sense to retry a few times. > the TaskTracker.Child.ping thread calls exit > -------------------------------------------- > > Key: HADOOP-133 > URL: http://issues.apache.org/jira/browse/HADOOP-133 > Project: Hadoop > Type: Bug > Components: mapred > Versions: 0.1.1 > Reporter: Owen O'Malley > Assignee: Owen O'Malley > > The TaskTracker.Child.startPinging thread calls exit if the TaskTracker > doesn't respond. Calling exit in a mutli-threaded program is really > problematic. In particular, it prevents cleanup/finally clauses from running. > We need to move to a model where it uses Thread.interrupt(), which means we > need to check the interrupt flag in place in the map loop and reduce loop and > stop masking the InterruptExceptions. -- 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
