hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wilfred Spiegelenburg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue
Date Thu, 30 Nov 2017 04:34:00 GMT

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

Wilfred Spiegelenburg commented on YARN-7562:
---------------------------------------------

I think you are going the wrong direction: this is not a code problem but a configuration
issue. Please read my previous update.

You are still breaking existing configurations and use cases. The _primaryGroup_ and _secondaryGroupExistingQueue_
can be used as the nested rule in the _nestedUserQueue_ rule as per the example that we have
in the [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/FairScheduler.html#Automatically_placing_applications_in_queues].
They must be allowed to return a parent queue.

> 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.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


Mime
View raw message