hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 牛兆捷 <nzjem...@gmail.com>
Subject Re: Yarn resource request
Date Fri, 22 Nov 2013 00:52:59 GMT
But I think there is some problems.

For example, the FIFO scheduler, the big memory request of a job may starve
as the small memory requests of other jobs can always be fulfilled. Is it
right?


2013/11/22 Bikas Saha <bikas@hortonworks.com>

> Yes.
>
> -----Original Message-----
> From: 牛兆捷 [mailto:nzjemail@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 resource
> for the higher priority container even the requirement of smaller
> container can be met.
>
>
> 2013/11/21 Bikas Saha <bikas@hortonworks.com>
>
> > 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 size amongst the sizes within a priority.
> >
> > Bikas
> >
> > -----Original Message-----
> > From: 牛兆捷 [mailto:nzjemail@gmail.com]
> > Sent: Wednesday, November 20, 2013 7:44 PM
> > To: yarn-dev@hadoop.apache.org
> > Subject: Yarn resource request
> >
> > Currently, resource requests for the same priority and locality are
> > expected to all be the same size, how will Application Master do for
> > different size? use different requests?
> >
> > --
> > *Regards,*
> > *Zhaojie*
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or
> > entity to which it is addressed and may contain information that is
> > confidential, privileged and exempt from disclosure under applicable
> > law. If the reader of this message is not the intended recipient, you
> > are hereby notified that any printing, copying, dissemination,
> > distribution, disclosure or forwarding of this communication is
> > strictly prohibited. If you have received this communication in error,
> > please contact the sender immediately and delete it from your system.
> Thank You.
> >
>
>
>
> --
> *Regards,*
> *Zhaojie*
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>



-- 
*Regards,*
*Zhaojie*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message