You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/04/24 19:03:09 UTC
[jira] Resolved: (HADOOP-157) job fails because pendingCreates is
not cleaned up after a task fails
[ http://issues.apache.org/jira/browse/HADOOP-157?page=all ]
Doug Cutting resolved HADOOP-157:
---------------------------------
Resolution: Fixed
I just committed this. Thanks, Owen!
> job fails because pendingCreates is not cleaned up after a task fails
> ---------------------------------------------------------------------
>
> Key: HADOOP-157
> URL: http://issues.apache.org/jira/browse/HADOOP-157
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.1.1
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.2
> Attachments: pending-creates-wait.patch
>
> When a task fails under map/reduce, if the client doesn't abandon the files in progress (usually because it was killed), the lease on the name node lasts 1 minute. During that minute, I see 3 backup copies of the task fail because pendingCreates is non-null.
--
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