You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/02/01 15:52:00 UTC
[jira] [Updated] (IMPALA-3922) Support
yarn.scheduler.fair.allow-undeclared-pools option in fair-scheduler.xml
[ https://issues.apache.org/jira/browse/IMPALA-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-3922:
----------------------------------
Summary: Support yarn.scheduler.fair.allow-undeclared-pools option in fair-scheduler.xml (was: Admission control pools are dynamically created even when dynamic queues are disabled in YARN)
> Support yarn.scheduler.fair.allow-undeclared-pools option in fair-scheduler.xml
> -------------------------------------------------------------------------------
>
> Key: IMPALA-3922
> URL: https://issues.apache.org/jira/browse/IMPALA-3922
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.3.0
> Reporter: Jim Halfpenny
> Priority: Minor
> Labels: admission-control, resource-management
>
> When the YARN parameter yarn.scheduler.fair.allow-undeclared-pools is set to false Impala still creates resource pools dynamically. This leads to unexpected behaviour when configuring admission controls.
> Impala uses the resource pool root.<username> if no pool is specified. Queries that do not
> specify a pool will trigger creation of a new one, which is likely not what the user intended. This behaviour occurs even when yarn.scheduler.fair.user-as-default-queue is set to false.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org