hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7778) Merging of constraints defined at different levels
Date Wed, 31 Jan 2018 07:29:01 GMT

    [ https://issues.apache.org/jira/browse/YARN-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346367#comment-16346367

Weiwei Yang commented on YARN-7778:

Test {{TestPlacementProcessor#testRePlacementAfterSchedulerRejection}} was not related, I
saw this several times in past jenkins reports, looks like a flaky one. The other one is tracked
via YARN-7860.

> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message