[
https://issues.apache.org/jira/browse/YARN-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347916#comment-16347916
]
Weiwei Yang commented on YARN-7778:
-----------------------------------
Hi [~kkaranasos]
Thanks for your comments, I agree with both #1 and #2 and get them done in next
patch. I also took a look #3, that code fragment removes null or dup entries in
a list of {{PlacementConstraint}} and then return us a list of
{{AbstractConstraint}}, it was not straightforward to me how other place is
going to re-use this. But let me know if you have a strong preference to do so.
Thanks.
> 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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
