sure

attached

Hopefully attachments are allowed

On Tue, Jan 10, 2017 at 11:07 PM, Terence Yim <cht...@gmail.com> wrote:

> Hi,
>
> I don’t see any attachment in your previous email. Would you mind
> attaching it again?
>
> Terence
> > On Jan 10, 2017, at 11:02 PM, Yuliya Feldman <yul...@dremio.com> wrote:
> >
> > Capacity scheduler
> >
> > On Tue, Jan 10, 2017 at 11:00 PM, Terence Yim <cht...@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> Do you know what resource schedule that YARN is running with?
> >>
> >> Terence
> >>
> >>> On Jan 6, 2017, at 10:32 AM, Yuliya Feldman <yul...@dremio.com> wrote:
> >>>
> >>> Yes, I did
> >>>
> >>> See attached
> >>>
> >>> On Fri, Jan 6, 2017 at 10:15 AM, Terence Yim <cht...@gmail.com
> <mailto:
> >> cht...@gmail.com>> wrote:
> >>> Hi,
> >>>
> >>> We've never observe this before. The AM container itself is always
> >> running
> >>> with 1 vcore. Have you look at the YARN container info in the RM UI
> that
> >> is
> >>> having that particular TwillRunnable running inside?
> >>>
> >>> Terence
> >>>
> >>> On Fri, Jan 6, 2017 at 9:54 AM, Yuliya Feldman <yul...@dremio.com
> >> <mailto:yul...@dremio.com>> wrote:
> >>>
> >>>> yes
> >>>>
> >>>> On Fri, Jan 6, 2017 at 9:40 AM, Terence Yim <cht...@gmail.com
> <mailto:
> >> cht...@gmail.com>> wrote:
> >>>>
> >>>>> Where do you verify the CPU cores? Was it from the YARN resource
> >> manager
> >>>>> UI?
> >>>>>
> >>>>> Terence
> >>>>>
> >>>>> Sent from my iPhone
> >>>>>
> >>>>>> On Jan 6, 2017, at 9:01 AM, Yuliya Feldman <yul...@dremio.com
> >> <mailto:yul...@dremio.com>> wrote:
> >>>>>>
> >>>>>> Sorry for so many questions - unfortunately not much information I
> >> can
> >>>>> fish
> >>>>>> in the wild :).
> >>>>>>
> >>>>>> I noticed that CPU count set on Application Specification is not
> >>>> getting
> >>>>>> reflected while starting container - it is always 1 CPU.
> >>>>>>
> >>>>>> Did anybody experience this? It really feels like it is lost
> >> somewhere
> >>>> in
> >>>>>> between Twill and YARN. I am using YARN 2.7.2
> >>>>>>
> >>>>>> Thanks in advance
> >>>>>
> >>>>
> >>>
> >>
> >>
>
>

Reply via email to