You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Benjamin Teke (Jira)" <ji...@apache.org> on 2026/10/07 09:05:00 UTC
[jira] [Created] (YARN-12015) Add a Capacity Scheduler queue configuration resolver with explicit inheritance and value sources
Benjamin Teke created YARN-12015:
------------------------------------
Summary: Add a Capacity Scheduler queue configuration resolver with explicit inheritance and value sources
Key: YARN-12015
URL: https://issues.apache.org/jira/browse/YARN-12015
Project: Hadoop YARN
Issue Type: Sub-task
Components: capacity scheduler
Reporter: Benjamin Teke
Assignee: Benjamin Teke
Defaults and inheritance rules for queue properties are spread across CapacitySchedulerConfiguration getters, settings classes and queue setup code.
Declare each per-queue property once (key, parser, applicable queue kinds, resolution chain: queue key, template, parent, global key, default; plus derivations such as absolute capacity and maximum applications) and add QueueConfigResolver, which produces an immutable ResolvedQueueConfig per queue in which every value records its source.
CapacitySchedulerConfiguration getters keep their signatures and delegate to the same descriptors, so each default and inheritance rule is defined once. Leaf queues, plan queues and the resolver share the maximum applications arithmetic (QueueApplicationLimits). Dynamic queue template values are read like trunk reads them after writing them into the configuration, including variables that reference other template entries. No behavior change should be implemented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org