[
https://issues.apache.org/jira/browse/MAPREDUCE-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804502#comment-14804502
]
Hudson commented on MAPREDUCE-5002:
-----------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #2349 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2349/])
MAPREDUCE-5002. AM could potentially allocate a reduce container to a map
attempt. Contributed by Chang Li (jlowe: rev
3f82f582e51c514cc0f052c828c2f58c6e8927ad)
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java
* hadoop-mapreduce-project/CHANGES.txt
> 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, 2.7.0
> Reporter: Jason Lowe
> Assignee: Chang Li
> Fix For: 2.8.0
>
> Attachments: MAPREDUCE-5002.1.patch, MAPREDUCE-5002.2.patch,
> MAPREDUCE-5002.2.patch, MAPREDUCE-5002.3.patch, MAPREDUCE-5002.4.patch,
> MAPREDUCE-5002.5.patch, MAPREDUCE-5002.6.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
