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 "Arun C Murthy (Updated) (JIRA)" <ji...@apache.org> on 2012/01/03 05:24:21 UTC

[jira] [Updated] (MAPREDUCE-3490) RMContainerAllocator counts failed maps towards Reduce ramp up

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

Arun C Murthy updated MAPREDUCE-3490:
-------------------------------------

    Attachment: MAPREDUCE-3490.patch

Thanks Sharad. I've updated your patch with unit tests. All of the re-factoring of RMContainerAllocator.scheduleReduces was to aid unit tests.
                
> RMContainerAllocator counts failed maps towards Reduce ramp up
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-3490
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3490
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Siddharth Seth
>            Assignee: Arun C Murthy
>            Priority: Blocker
>         Attachments: MAPREDUCE-3490.patch, MAPREDUCE-3490.patch, MAPREDUCE-3490.patch, MAPREDUCE-3490.patch, MAPREDUCE-3490.patch, MR-3490-alternate.patch, MR-3490-alternate1.patch
>
>
> The RMContainerAllocator does not differentiate between failed and successful maps while calculating whether reduce tasks are ready to launch. Failed tasks are also counted towards total completed tasks. 
> Example. 4 failed maps, 10 total maps. Map%complete = 4/14 * 100 instead of being 0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira