[
https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299449#comment-16299449
]
Arun Suresh commented on YARN-6596:
-----------------------------------
Also just a thought.
Clients of the API might not probably if it is dealing with a global constraint
or an application constraint (atleast until we have a cluster admin level API).
Would it not be better if we just expose addConstraint(sourceTags, constraint,
appId) and getConstraint(sourceTags, appId) and let the
PlacementConstaintManager decide from the tags if it is app specific or global
and perform the appropriate operation ?
> Introduce Placement Constraint Manager module
> ---------------------------------------------
>
> Key: YARN-6596
> URL: https://issues.apache.org/jira/browse/YARN-6596
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Attachments: YARN-6596-YARN-6592.001.patch
>
>
> This RM module will be responsible for storing placement constraints,
> allocation tags, and node attributes.
> It will be used when determining the placement of SchedulingRequests with
> constraints.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
