Running and Pending Application Limits
Applications are considered active if they are either running or pending. The following table lists properties that specify running and pending application limits:
| Property | Description |
|---|---|
yarn.scheduler.capacity.
maximum-applications
|
Maximum number of applications in the system that can be concurrently active, both running and pending. Limits on each queue are directly proportional to their queue capacities and user limits. This is a hard limit; any applications submitted when this limit is reached will be rejected. The default is 10000. This applies to all queues. |
yarn.scheduler.capacity.
<queue-path>.maximum-applications
|
Overrides
yarn.scheduler.capacity.maximum-applications on a per
queue basis. |
yarn.scheduler.capacity.
maximum-am-resource-percent
|
Maximum percent of resources in the cluster that can be used to run application masters - controls the number of concurrent active applications. Limits on each queue are directly proportional to their queue capacities and user limits. Specified as a float. For example, 0.5 = 50%. The default is 0.1. This can be set for all queues with yarn.scheduler.capacity.maximum-am-resource-percent |
yarn.scheduler.capacity.
<queue-path>.maximum-am-resource-percent
|
Overrides
yarn.scheduler.capacity.maximum-am-resource-percent on
a per queue basis. |