[ http://issues.apache.org/jira/browse/HADOOP-133?page=comments#action_12374976 ]
Doug Cutting commented on HADOOP-133: ------------------------------------- Searching around a bit, I found a few folks who suggest using -Xrs if you're seeing exit code 143, since this can be caused by signals. So you might try adding -Xrs to mapred.child.java.opts and see if that helps any. > 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
