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-39) Job killed when backup tasks fail
Date Thu, 27 Jul 2006 03:18:14 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-39?page=comments#action_12423760 ] 
Owen O'Malley commented on HADOOP-39:

My goal with this would be to do the equivalent of "make -k" or a "best effort" job. It the
option was set, the job would continue after a given TIP had failed 4 times, but that TIP
would be abandoned.

> Job killed when backup tasks fail
> ---------------------------------
>                 Key: HADOOP-39
>                 URL: http://issues.apache.org/jira/browse/HADOOP-39
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Owen O'Malley
> I had a map job with side effects that meant that any speculative tasks would fail.
> Currently, the job tracker kills the job when the speculative task fails 4 times.
> It would be better to stop scheduling speculative tasks for that fragment, but let the
job continue as long as one of the the instances of that fragment continue to run.

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


View raw message