ty
>
> Maximum queue capacity in percentage (%) as a float. This limits the
> *elasticity* for applications in the queue. Defaults to -1 which disables
> it.
>
>
>
> 2. Preemption of containers.
>
>
>
>
>
> Regards
>
> Bibin
>
>
>
> *
usecase specifically for per node allocation based on
> percentage?
>
>
>
>
>
> *From:* Rafał Radecki [mailto:radecki.ra...@gmail.com]
> *Sent:* 10 November 2016 14:59
> *To:* Ravi Prakash
> *Cc:* user
> *Subject:* Re: Yarn 2.7.3 - capacity scheduler container allocation
your
> application could request to be run on only the nodes which have GPUs)
>
> HTH
> Ravi
>
> On Wed, Nov 9, 2016 at 5:37 AM, Rafał Radecki
> wrote:
>
>> Hi All.
>>
>> I have a 4 node cluster on which I run yarn. I created 2 queues "long"
Hi All.
I have a 4 node cluster on which I run yarn. I created 2 queues "long" and
"short", first with 70% resource allocation, the second with 30%
allocation. Both queues are configured on all available nodes by default.
My memory for yarn per node is ~50GB. Initially I thought that when I will
Hi All.
I configured yarn to use capacity scheduler, I have for physical nodes. On
first of them I run resourcemanager and nodemanager on all of them.
My capacity-scheduler.xml and yarn-site.yml are attached.
When I submit a job to the "long" queue I get in resourcemanager's logfile
the content o
