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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/03/31 23:41:15 UTC

[jira] [Commented] (MAPREDUCE-5002) AM could potentially allocate a reduce container to a map attempt

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

Bikas Saha commented on MAPREDUCE-5002:
---------------------------------------

The fix might be to allow MAP to use FAILED_MAP priority but not REDUCE. For reduce, we could release excess REDUCE containers in the loop inside ScheduledRequests.assign() by checking against reduces.size() instead of reduces.isEmpty().
                
> AM could potentially allocate a reduce container to a map attempt
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-5002
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5002
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 2.0.3-alpha, 0.23.7
>            Reporter: Jason Lowe
>
> As discussed in MAPREDUCE-4982, after MAPREDUCE-4893 it is theoretically possible for the AM to accidentally assign a reducer container to a map attempt if the AM doesn't find a reduce attempt actively looking for the container (e.g.: the RM accidentally allocated too many reducer containers).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira