Quantcast
Channel: Hortonworks » All Replies
Viewing all articles
Browse latest Browse all 3435

Reply To: CapacityScheduler not being elastic

$
0
0

So, I think I may have answered my own question. I was running my test jobs as one user and I see that I have

yarn.scheduler.capacity.root.ingestion.user-limit-factor=1

meaning that no one user can use more than 1 of the queues’ capacity.

From http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1.3/bk_system-admin-guide/content/setting_user_limits.html

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.


Viewing all articles
Browse latest Browse all 3435

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>