hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-158) mapred.userlog.retain.hours killing long running tasks
Date Fri, 16 Oct 2009 04:53:31 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766410#action_12766410

Vinod K V commented on MAPREDUCE-158:

This issue is circumvented after HADOOP-4374 and so is not visible beyond 0.20.

The reason why logs of running tasks are no longer cleaned up causing failures is that HADOOP-4374
introduced log.tmp for atomicity of changes to log.index which is periodically created and
written to by a running task. This results in a periodic change in modification time of attempt-log
directory and prevents its cleanup even though _mapred.userlog.retain.hours_ is over.

So what should be done here? Close this issue? Or make the check for running tasks explicit
during cleanup?

> mapred.userlog.retain.hours killing long running tasks
> ------------------------------------------------------
>                 Key: MAPREDUCE-158
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-158
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>         Environment: 0.19.2-dev, r753365 
>            Reporter: Billy Pearson
>         Attachments: hadoop-5600.patch
> One can reproduce the scenario by configuring mapred.userlog.retain.hours to 1hr, and
running tasks that take more than an hour.
> More info on closed ticket HADOOP-5591.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message