[
https://issues.apache.org/jira/browse/MAPREDUCE-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573380#comment-13573380
]
Hudson commented on MAPREDUCE-4671:
-----------------------------------
Integrated in Hadoop-Yarn-trunk #120 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/120/])
MAPREDUCE-4671. AM does not tell the RM about container requests which are
no longer needed. Contributed by Bikas Saha. (Revision 1443323)
Result = FAILURE
sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443323
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerRequestor.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java
> AM does not tell the RM about container requests that are no longer needed
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-4671
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4671
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.3, 2.0.0-alpha
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Fix For: 2.0.4-beta
>
> Attachments: MAPREDUCE-4671.1.patch, MAPREDUCE-4671.2.patch,
> MAPREDUCE-4671.3.patch, MAPREDUCE-4671.4.patch, MAPREDUCE-4671.txt
>
>
> Say the AM wanted a container at hosts h1, h2, h3. After getting a container
> at h1 it should tell RM that it no longer needs containers at h2, h3.
> Otherwise on the RM h2, h3 remain valid allocation locations.
> The AM RMContainerAllocator does remove these resource requests internally.
> When the resource request container count drops to 0 then it drops the
> resource request from its tables but forgets to send the 0 sized request to
> the RM.
--
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
