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 "Anupam Seth (Assigned) (JIRA)" <ji...@apache.org> on 2012/04/06 15:53:23 UTC
[jira] [Assigned] (MAPREDUCE-2694) AM releases too many containers
due to the protocol
[ https://issues.apache.org/jira/browse/MAPREDUCE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anupam Seth reassigned MAPREDUCE-2694:
--------------------------------------
Assignee: Anupam Seth
> AM releases too many containers due to the protocol
> ---------------------------------------------------
>
> Key: MAPREDUCE-2694
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2694
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Arun C Murthy
> Assignee: Anupam Seth
>
> - AM sends request asking 4 containers on host H1.
> - Asynchronously, host H1 reaches RM and gets assigned 4 containers. RM at this point, sets the value against H1 to
> zero in its aggregate request-table for all apps.
> - In the mean-while AM gets to need 3 more containers, so a total of 7 including the 4 from previous request.
> - Today, AM sends the absolute number of 7 against H1 to RM as part of its request table.
> - RM seems to be overriding its earlier value of zero against H1 to 7 against H1. And thus allocating 7 more
> containers.
> - AM already gets 4 in this scheduling iteration, but gets 7 more, a total of 11 instead of the required 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira