[
https://issues.apache.org/jira/browse/MAPREDUCE-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472865#comment-13472865
]
Siddharth Seth commented on MAPREDUCE-4671:
-------------------------------------------
iirc, blacklisting the node changes the request directly in the
RMContainerRequestor. When the RMContainerAllocator removes a previous ask
(assigned task, etc) - it includes the blacklisted host in this request.
Asserting the value never goes below 0 - will need to change this behaviour.
Otherwise a simple check and ignore is sufficient.
> 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
> Attachments: MAPREDUCE-4671.1.patch, MAPREDUCE-4671.2.patch
>
>
> 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
