never
execeed first queues capacity
On 4/28/11 11:48 PM, "Rosanna Man" wrote:
Hi all,
We are using capacity scheduler to schedule resources among different queues
for 1 user (hadoop) only. We have set the queues to have equal share of the
resources. However, when 1st task start
cheduler does not have pre-emption. So basically when the
>>> Job1 starts finishing and freeing up the Job2¹s tasks will start getting
>>> scheduled. One way you can prevent that queue capacities are not elastic in
>>> nature is by setting max task limits on queues. That
on queues. That way your job1 will never
execeed first queues capacity
On 4/28/11 11:48 PM, "Rosanna Man" wrote:
Hi all,
We are using capacity scheduler to schedule resources among different queues
for 1 user (hadoop) only. We have set the queues to have equal share of the
resourc
hat way your job1 will never
> execeed first queues capacity
>
>
>
>
> On 4/28/11 11:48 PM, "Rosanna Man" wrote:
>
>> Hi all,
>>
>> We are using capacity scheduler to schedule resources among different queues
>> for 1 user (hadoop)
your job1 will never
execeed first queues capacity
On 4/28/11 11:48 PM, "Rosanna Man" wrote:
Hi all,
We are using capacity scheduler to schedule resources among different queues
for 1 user (hadoop) only. We have set the queues to have equal share of the
resources. However, when 1st
Hi all,
We are using capacity scheduler to schedule resources among different queues
for 1 user (hadoop) only. We have set the queues to have equal share of the
resources. However, when 1st task starts in the first queue and is consuming
all the resources, the 2nd task starts in the 2nd queue
