hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-133) the TaskTracker.Child.ping thread calls exit
Date Thu, 13 Apr 2006 23:18:00 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-133?page=comments#action_12374433 ] 

Owen O'Malley commented on HADOOP-133:

I've been assuming that the "Child died with nonzero exit status" with no other error messages
is coming from the failure of a ping. I will change that message to include the actual exit
status and change the ping-failure exit code to 123 or something.

> 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:
For more information on JIRA, see:

View raw message