[
https://issues.apache.org/jira/browse/MAPREDUCE-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573006#comment-13573006
]
Siddharth Seth commented on MAPREDUCE-4984:
-------------------------------------------
Sandy, is this a dupe of MAPREDUCE-4671 ?
> AM leaves unwanted node/rack requests after container has been assigned
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-4984
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4984
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: applicationmaster, mr-am
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
>
> Consider the following situation:
> node1, node2, and node3 are all on rack1
> task1 is submitted with resource requests on node1, node2, rack1, and *
> task2 is submitted with resource requests on node3, rack1, and *
> The RM gives a container to the app on node1, on which the AM assigns task1.
> While node1 is removed from the scheduler's bookkeeping, node2 is not, so its
> delay scheduling will try as hard to assign a container there is it would to
> node3.
> The AM should cancel its request for node2 on its next heartbeat by sending a
> resource request with # containers = 0.
--
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
