hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4671) AM does not tell the RM about container requests that are no longer needed
Date Sun, 07 Oct 2012 22:34:04 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471346#comment-13471346
] 

Bikas Saha commented on MAPREDUCE-4671:
---------------------------------------

I think we can assert that the value should never go below 0 because that would mean we are
trying to remove more containers than we requested, which would be an app bug.
                
> 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

Mime
View raw message