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 "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2009/05/22 07:58:45 UTC

[jira] Updated: (HADOOP-5882) Progress is not updated when the New Reducer is running reduce phase

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

Amareshwari Sriramadasu updated HADOOP-5882:
--------------------------------------------

             Priority: Blocker  (was: Major)
    Affects Version/s: 0.20.0
        Fix Version/s: 0.20.1

Marking it a blocker, I see reducers failing because they couldn't report status for 600 seconds, during reduce phase.

> Progress is not updated when the New Reducer is running reduce phase
> --------------------------------------------------------------------
>
>                 Key: HADOOP-5882
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5882
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.20.0
>            Reporter: Jothi Padmanabhan
>            Priority: Blocker
>             Fix For: 0.20.1
>
>
> The old reducer calls informReduceProgress on a key change to update the progress. This call or equivalent should be called for the new reducer as well.

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