# Support Questions

Announcements
Celebrating as our community reaches 100,000 members! Thank you!

## What is the significance of user limit factor while configuring queues in yarn queue manager in ambari?

Expert Contributor

2 ACCEPTED SOLUTIONS
Contributor

Hi @Ram D

The explanation for the parameter is:

The multiple of the queue capacity which can be configured to allow a single user to acquire more resources. By default this is set to 1 which ensures that a single user can never take more than the queue's configured capacity irrespective of how idle the cluster is. Value is specified as a float.

There are two queue parms capacity and max capacity.

The max determines elasticity and it is at queue level.

We have to adjust the user-limit-factor so that user can leverage more than just the capacity. What it says is a user can use X number of times the capacity of the queue within under max capacity.

Hope this helps !

Contributor

If you put User Limit Factor as 3.5 it will take over the minimum queue capacity and will go towards max capacity of the queue.
Let's say if the Minimum capacity of queue is 20% putting user limit factor of 3.5 will give the user to get resources till 70% if that limit is within the max limit of the queue other the queues max limit will be the limit for the user.

6 REPLIES 6
Expert Contributor

@Neeraj Sabharwal @Artem Ervits Can anyone help me with explanation? if i put user limit factor as 3.5, what it will do?

Contributor

If you put User Limit Factor as 3.5 it will take over the minimum queue capacity and will go towards max capacity of the queue.
Let's say if the Minimum capacity of queue is 20% putting user limit factor of 3.5 will give the user to get resources till 70% if that limit is within the max limit of the queue other the queues max limit will be the limit for the user.

Contributor
Expert Contributor

I am asking about user limit factor in yarn queue manager? if we click on created queue under root, it shows user limit factor. what is the significance of it?

Contributor

Hi @Ram D

The explanation for the parameter is:

The multiple of the queue capacity which can be configured to allow a single user to acquire more resources. By default this is set to 1 which ensures that a single user can never take more than the queue's configured capacity irrespective of how idle the cluster is. Value is specified as a float.

There are two queue parms capacity and max capacity.

The max determines elasticity and it is at queue level.

We have to adjust the user-limit-factor so that user can leverage more than just the capacity. What it says is a user can use X number of times the capacity of the queue within under max capacity.

Hope this helps !

Expert Contributor