You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Weiwei Yang (JIRA)" <ji...@apache.org> on 2018/02/01 02:22:00 UTC
[jira] [Updated] (YARN-7778) Merging of constraints defined at
different levels
[ https://issues.apache.org/jira/browse/YARN-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weiwei Yang updated YARN-7778:
------------------------------
Attachment: YARN-7778.003.patch
> Merging of constraints defined at different levels
> --------------------------------------------------
>
> Key: YARN-7778
> URL: https://issues.apache.org/jira/browse/YARN-7778
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Konstantinos Karanasos
> Assignee: Weiwei Yang
> Priority: Major
> Attachments: Merge Constraints Solution.pdf, YARN-7778-YARN-7812.001.patch, YARN-7778-YARN-7812.002.patch, YARN-7778.003.patch
>
>
> When we have multiple constraints defined for a given set of allocation tags at different levels (i.e., at the cluster, the application or the scheduling request level), we need to merge those constraints.
> Defining constraint levels as cluster > application > scheduling request, constraints defined at lower levels should only be more restrictive than those of higher levels. Otherwise the allocation should fail.
> For example, if there is an application level constraint that allows no more than 5 HBase containers per rack, a scheduling request can further restrict that to 3 containers per rack but not to 7 containers per rack.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org