[
https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961035#comment-14961035
]
Bikas Saha commented on YARN-1509:
----------------------------------
Does issuing an increase followed by the decrease actually remove the pending
change request on the RM or will it cause the RM to try to change a container
resource to the same size as the existing resource and then go down the code
path of increase (new token) or decrease (update NM). This would be a corner
case that would be good to double check. If that works and the RM actually
removes the pending container change request then we could use this mechanism
to implement a cancel method wrapper in the AMRMClient. Otherwise, if fixes are
needed on the RM side, we could so it separately when we fix the RM.
> Make AMRMClient support send increase container request and get
> increased/decreased containers
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-1509
> URL: https://issues.apache.org/jira/browse/YARN-1509
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Wangda Tan (No longer used)
> Assignee: MENG DING
> Attachments: YARN-1509.1.patch, YARN-1509.2.patch, YARN-1509.3.patch,
> YARN-1509.4.patch, YARN-1509.5.patch
>
>
> As described in YARN-1197, we need add API in AMRMClient to support
> 1) Add increase request
> 2) Can get successfully increased/decreased containers from RM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
