[
https://issues.apache.org/jira/browse/YARN-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328105#comment-16328105
]
Wangda Tan commented on YARN-6619:
----------------------------------
[~kkaranasos] , is this supported?
{quote}bq. This way we can reserve the {{addPlacementConstraint}} API for
cases that a client wants to update the constraints.
{quote}
IIUC, the only way to update PlacementConstraint, as well as pending
ResourceSizing, is to send a new SchedulingRequest correct? If there's no
separate updatePlacementConstraint API, I suggest to remove
addPlacementConstraint from AMRMClient as of now and add it back when needed.
> AMRMClient Changes to use the PlacementConstraint and SchcedulingRequest
> objects
> --------------------------------------------------------------------------------
>
> Key: YARN-6619
> URL: https://issues.apache.org/jira/browse/YARN-6619
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Priority: Major
> Attachments: YARN-6619-YARN-6592.001.patch,
> YARN-6619-YARN-6592.002.patch
>
>
> Opening this JIRA to track changes needed in the AMRMClient to incorporate
> the PlacementConstraint and SchedulingRequest objects
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
