[
https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300053#comment-16300053
]
Sunil G commented on YARN-6596:
-------------------------------
bq.Note that constraints can be defined at three levels: at the cluster level,
at the application level, and at the scheduling request level.
Probably if we had constraints only at the scheduling request level, we could
do without Placement Constraint Manager.
[~kkaranasos], Yes. I guess node-constraints will be at node level and we need
not have to handle it in Placement Constraint Manager. However I am not very
sure about the global constraint which you mentioned in this patch. When
YARN-3409 is coming in, admin could set few constraints and placement manager
may might derive its to map to app's demand. Could you provide more clarity on
this global constraints (use case).
NodeLabelManager already have in-memory, file, zk(wip). Could we some how reuse
or do in same line to reuse or formalize similar placement related infos.
> 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]
