Field Name | Parameter | Description |
Resource Pool Name | yarn.scheduler.capacity.<queue-path>.queues</queue-path> | Name of the resource pool or queue |
Label Settings | N/A | Set the specified label that can be accessed by the queue. |
Capacity | yarn.scheduler.capacity.<queue-path>.capacity</queue-path> | Available resource amount. The total capacity of the subpools of a parent pool is 100. Available resource amount = resource amount of the parent pool * percentage set here. The queue can consume more resources than the queue's capacity if there are idle resources in other queues. |
Max Capacity | yarn.scheduler.capacity.<queue-path>.maximum-capacity</queue-path> | Maximum queue capacity in percentage. Because of resource sharing, the amount of resources used by a queue may exceed its capacity, and this field specifies the maximum amount of resources that can be used by the queue. |
Default Label Expression | yarn.scheduler.capacity.<queue-path>.default-node-label-expression</queue-path> | If a resource request does not have a node label specified, the application will be submitted to the corresponding partition specified by this configuration item. By default, the value is empty, i.e., applications will be allocated to containers on nodes with no label. |
Min User Capacity | yarn.scheduler.capacity.<queue-path>.minimum-user-limit-percent</queue-path> | Minimum resources in percentage guaranteed for each user. Each queue enforces a limit on the percentage of resources allocated to a user at any given time. When multiple users' applications are running in a queue concurrently, the amount of resources used by each user varies between a minimum and maximum value. The minimum value depends on the number of running applications, and the maximum value is determined by `minimum-user-limit-percent`. |
User Resource Factor | yarn.scheduler.capacity.<queue-path>.user-limit-factor</queue-path> | Maximum amount of resources in percentage that can be used by each user. For example, if the value is `30`, the amount of resources for each user cannot exceed 30% of the queue capacity at any given time. |
Max Memory per Container | yarn.scheduler.capacity.<queue-path>.maximum-allocation-mb</queue-path> | Maximum memory that can be allocated to each container. The value will overwrite and cannot be greater than that of the system's `yarn.scheduler.maximum-allocation-mb`. |
Max vCores per Container | yarn.scheduler.capacity.<queue-path>.maximum-allocation-vcores</queue-path> | Maximum number of CPU cores that can be allocated to each container. The value will overwrite and cannot be greater than that of the system's `yarn.scheduler.maximum-allocation-vcores`. |
Resource Pool Status | yarn.scheduler.capacity.<queue-path>.state</queue-path> | Status of the queue. The value can be `Running` or `Stopped`. If a queue is in the `Stopped` status, new applications cannot be submitted to it or any of its subqueues. |
Max Apps | yarn.scheduler.capacity.<queue-path>.maximum-applications</queue-path> | Maximum number of concurrent active (both running and pending) applications allowed in the system |
Max Resources for AM | yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent</queue-path> | Maximum percentage of resources in the cluster which can be used to run application masters. It controls the number of concurrent active applications. |
Resource Pool Priority | yarn.scheduler.capacity.root.<leaf-queue-path>.default-application-priority</leaf-queue-path> | Configure the priority of the resource queue, which is `0` by default. The larger the value, the higher the priority. |
Submission | yarn.scheduler.capacity.root.<queue-path>.acl_submit_applications | List of users that can submit apps to the queue |
Management | yarn.scheduler.capacity.root.<queue-path>.acl_administer_queue | List of users that can manage the queue |
Delayed Scheduling | yarn.scheduler.capacity.node-locality-delay | Set the allowed number of times of delayed scheduling to ensure the local execution of tasks. If the value is `-1`, delayed scheduling will be disabled. |
default
and Overwrite Specified Queues is enabled, the mapped queue will be used; otherwise, the specified queue will be used.
Was this page helpful?