@Hoang Le Capacity Scheduler’s leaf queues can also use the user-limit-factor property to control user resource allocations. This property denotes the fraction of queue capacity that any single user can consume up to a maximum value, regardless of whether or not there are idle resources in the cluster. Property: yarn.scheduler.capacity.root.support.user-limit-factor Value: 1 The default value of "1" means that any single user in the queue can at maximum only occupy the queue’s configured capacity. This prevents users in a single queue from monopolizing resources across all queues in a cluster. Setting the value to "2" would restrict the queue's users to twice the queue’s configured capacity. Setting it to a value of 0.5 would restrict any user from using resources beyond half of the queue capacity. These settings can also be dynamically changed at run-time using yarn rmadmin - refreshQueues . Please change user limit factor and try. ... View more

@Hoang Le The max application master resource is calculated using the value "yarn.scheduler.capacity.maximum-am-resource-percent" which is set in capacity-scheduler.xml. The default value is 0.1 which means 10% of the cluster resources. More info can be found in http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.4.0/bk_yarn_resource_mgt/content/setting_application_limits.html ... View more