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] Updated: (HADOOP-133) the TaskTracker.Child.ping thread calls exit
Date Tue, 18 Apr 2006 21:47:18 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-133?page=all ]

Owen O'Malley updated HADOOP-133:

    Attachment: ping-stability.patch

Here is a patch that allows retries for communication problems on the ping from the Task to
the TaskTracker. It changes the interface of ping from returning nothing to returning a boolean.
A false return value means the child should immediately go away. Exceptions are treated as
temporary problems and given 3 chances. This patch also changes the exit code to be either
65 (asked to kill self) or 66 (ping exception).

> 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
>  Attachments: ping-stability.patch
> 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