hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Templeton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4975) Fair Scheduler: exception thrown when a parent queue marked 'parent' has configured child queues
Date Thu, 26 Jan 2017 22:13:24 GMT

     [ https://issues.apache.org/jira/browse/YARN-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Templeton updated YARN-4975:
-----------------------------------
    Fix Version/s: 2.9.0

> Fair Scheduler: exception thrown when a parent queue marked 'parent' has configured child
queues
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4975
>                 URL: https://issues.apache.org/jira/browse/YARN-4975
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.7.2
>            Reporter: Ashwin Shankar
>            Assignee: Yufei Gu
>             Fix For: 2.9.0, 3.0.0-alpha3
>
>         Attachments: YARN-4975.001.patch, YARN-4975.002.patch
>
>
> We upgraded our clusters to 2.7.2 from 2.4.1 and saw the following exception in RM logs
:
> {code}
> Caused by: org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AllocationConfigurationException:
Both <reservation> and type="parent" found for queue root.adhoc which is unsupported
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AllocationFileLoaderService.loadQueue(AllocationFileLoaderService.java:519)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AllocationFileLoaderService.reloadAllocations(AllocationFileLoaderService.java:352)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.initScheduler(FairScheduler.java:1440)
> {code}
> From the exception, it looks like we've configured 'reservation', but we've not. The
issue is that AllocationFileLoaderService#loadQueue assumes that a parent queue marked as
'type=parent' cannot have configured child queues. That can be a problem in cases where we
mark a queue as 'parent' which has no configured child queues to start with, but we can add
child queues later on.
> Also the exception message is kind of misleading since we haven't configured 'reservation'.

> How to reproduce:
> Run fair scheduler with following queue config:
> {code}
> <queue name="p" type="parent">
>         <weight>10</weight>
>         <maxRunningApps>300</maxRunningApps>
>         <queue name="c">
>             <weight>3</weight>
>          </queue>
> </queue>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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