..@gmail.com]
> Sent: Thursday, November 21, 2013 12:54 AM
> To: yarn-dev@hadoop.apache.org
> Subject: Re: Yarn resource request
>
> Then, if one application master request for two different size container
> with different priority, the resource manager will reserve the reso
Yes.
-Original Message-
From: 牛兆捷 [mailto:nzjem...@gmail.com]
Sent: Thursday, November 21, 2013 12:54 AM
To: yarn-dev@hadoop.apache.org
Subject: Re: Yarn resource request
Then, if one application master request for two different size container
with different priority, the resource
I'm trying to track which servers aren't running a copy of my container
(HBase RS, Accumulo Tablet), yet were running them recently -so I keep a
list of recently used servers, write that to disk after changes, on startup
reread the latest re-readable version and rebuild that list.
I want to know w
On receive node update event, scheduler will assign resources of this node
to containers, isn't it?
Why you say we can not know which one is satisfied?
I do not know what your code do? Testing resource request of response of
resource manager? How to run it?
2013/11/21 Steve Loughran
> On 21 N
On 21 November 2013 09:04, 牛兆捷 wrote:
> Another question.
>
> For two request with the same priority, which one will be chosen?
>
No way to know. An equally interesting question is : how do you know which
one has been satisfied, and which one is oustanding?
I spent some time trying to do some o
Another question.
For two request with the same priority, which one will be chosen?
2013/11/21 Bikas Saha
> That’s a known limitation of the current implementation of schedulers in
> YARN. The API allows different requests of different sizes within the same
> priority but the implementations o
Then, if one application master request for two different size container
with different priority, the resource manager will reserve the resource for
the higher priority container even the requirement of smaller container can
be met.
2013/11/21 Bikas Saha
> That’s a known limitation of the curre
That’s a known limitation of the current implementation of schedulers in
YARN. The API allows different requests of different sizes within the same
priority but the implementations of the schedulers do not support this.
For different sizes, one can either use different priorities or use the
highest
