[
https://issues.apache.org/jira/browse/YARN-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284429#comment-16284429
]
Hudson commented on YARN-7520:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13350 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13350/])
YARN-7520. Queue Ordering policy changes for ordering auto created leaf
(wangda: rev a8316df8c05a7b3d1a5577174b838711a49ef971)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/policy/TestPriorityUtilizationQueueOrderingPolicy.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/policy/PriorityUtilizationQueueOrderingPolicy.java
> Queue Ordering policy changes for ordering auto created leaf queues within
> Managed parent Queues
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-7520
> URL: https://issues.apache.org/jira/browse/YARN-7520
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Fix For: 3.1.0
>
> Attachments: YARN-7520.1.patch, YARN-7520.2.patch, YARN-7520.3.patch,
> YARN-7520.4.patch, YARN-7520.5.patch, YARN-7520.6.patch
>
>
> Queue Ordering policy currently uses priority, utilization and absolute
> capacity for pre-configured parent queues to order leaf queues while
> assigning containers. It needs modifications for auto created leaf queues
> since they can have zero capacity
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
