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 "Wilfred Spiegelenburg (JIRA)" <ji...@apache.org> on 2017/12/01 12:00:00 UTC
[jira] [Commented] (YARN-7562) queuePlacementPolicy should not
match parent queue
[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274302#comment-16274302 ]
Wilfred Spiegelenburg commented on YARN-7562:
---------------------------------------------
That looks better. Still needs a lot of cleanup, you cannot leave any checkstyle and or whitespace failures. The TestNodeLabelContainerAllocation is a known failure and covered in a different jira.
The test should also be simplified:
* remove the 'primaryGroup' and 'secondaryGroupExistingQueue' rules
* remove the queues 'root.user1group' and 'root.user1subgroup1'
* change the assignAppToQueue call to clearly distinguish possible failures: use a different queue name as the provided queue name.
However this change is not backwards compatible. It changes the way the policy works It should be marked as an incompatible change
> queuePlacementPolicy should not match parent queue
> --------------------------------------------------
>
> Key: YARN-7562
> URL: https://issues.apache.org/jira/browse/YARN-7562
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: fairscheduler, resourcemanager
> Affects Versions: 2.7.1
> Reporter: chuanjie.duan
> Attachments: YARN-7562.002.patch, YARN-7562.003.patch, YARN-7562.004.patch, YARN-7562.patch
>
>
> User algo submit a mapreduce job, console log said "root.algo is not a leaf queue exception".
> root.algo is a parent queue, it's meanless for me. Not sure why parent queue added before
> <queue name="default">
> <minResources>3000 mb, 1 vcores</minResources>
> <maxResources>24000 mb, 8 vcores</maxResources>
> <maxRunningApps>4</maxRunningApps>
> <weight>1</weight>
> <schedulingMode>fifo</schedulingMode>
> </queue>
> <queue name="cim">
> <minResources>3000 mb, 1 vcores</minResources>
> <maxResources>24000 mb, 8 vcores</maxResources>
> <maxRunningApps>4</maxRunningApps>
> <weight>1</weight>
> <schedulingMode>fifo</schedulingMode>
> </queue>
> <queue name="algo">
> <minSharePreemptionTimeout>300</minSharePreemptionTimeout>
> <minResources>40000 mb, 10 vcores</minResources>
> <maxResources>200000 mb, 60 vcores</maxResources>
> <queue name="testb">
> <minSharePreemptionTimeout>300</minSharePreemptionTimeout>
> <minResources>40000 mb, 10 vcores</minResources>
> <maxResources>100000 mb, 30 vcores</maxResources>
> <maxRunningApps>20</maxRunningApps>
> <schedulingMode>fifo</schedulingMode>
> <weight>4</weight>
> </queue>
> <queue name="testa">
> <minSharePreemptionTimeout>300</minSharePreemptionTimeout>
> <minResources>40000 mb, 10 vcores</minResources>
> <maxResources>100000 mb, 30 vcores</maxResources>
> <maxRunningApps>20</maxRunningApps>
> <schedulingMode>fifo</schedulingMode>
> <weight>4</weight>
> </queue>
> </queue>
> <queuePlacementPolicy>
> <rule name="user" create="false" />
> <rule name="specified" />
> <rule name="default" queue="default"/>
> </queuePlacementPolicy>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org