You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Christian Kunz (JIRA)" <ji...@apache.org> on 2009/10/16 19:34:31 UTC

[jira] Resolved: (MAPREDUCE-83) Job completion delayed

     [ https://issues.apache.org/jira/browse/MAPREDUCE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Kunz resolved MAPREDUCE-83.
-------------------------------------

      Resolution: Duplicate
    Release Note: This is a duplicate of MAPREDUCE-114 (with a more mnemonic title). At least, somebody else ran into the same issue :)

> Job completion delayed
> ----------------------
>
>                 Key: MAPREDUCE-83
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-83
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Christian Kunz
>
> A job with all reduces completed but with some incomplete re-executed maps is not declared complete till all tasks are complete.
> Couldn't the incomplete maps just be killed off?
> Even if maps write to dfs directly, these incomplete maps must have been successful before, so there should be no reason to wait for them.

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