[
https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961090#comment-14961090
]
Wangda Tan commented on YARN-1509:
----------------------------------
Sync up with [~mding]. I think we're all on the same page now. Some thoughts
from my side:
- We can separate cancel container resource request change to a separated JIRA.
Now using decrease container to same size to cancel pending increase request is
like a workaround, we'd better add a protocol to AMRMProtocol so AMRMClient can
do things correct.
- For the onContainerResourceChanged API
{code}
public abstract void onContainersResourceChanged(List<Container> containers);
{code}
This looks good to me. Since we have a unified API to request change container,
return the updated container to AM should be enough, AM knows if it's an
increased or decreased container.
Thoughts? [~bikassaha].
> 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)
