>...the zero profiles still allocated containers even though the setting
was 1 and
> the NM had < 1 available vcores. So I am still trying to figure out why
> this worked in this use case so I am clear on the setting.
The myriad scheduler running inside the RM dynamically changes the RM's
perspe
So I am still confused by the FGS/mininum-allocation-vcores.
>> This also implicitly means that YARN cannot allocate a container unless
at least "min allocation vcores" are available on a NM. If a NM has less
than
"miin allocation vcores", that NM will not get any containers allocated to
it, unles
Thanks for trying out these experiments.
>I thought this would have
>broken FGS, but apparently it didn't (I started my nodes with min
>allocation CPU = 1 and FGS still worked for me... not sure about that,
>would love feedback there)
I presume you are referring to "yarn.scheduler.minimum-allocat
Great to hear!!!
Thank you John.
Yuliya
From: John Omernik
To: dev@myriad.incubator.apache.org
Sent: Tuesday, November 24, 2015 9:25 AM
Subject: A Myriad Story
Since a vast majority of my posts are me struggling with something or
breaking something, I thought I'd take the ti
Since a vast majority of my posts are me struggling with something or
breaking something, I thought I'd take the time to craft a story of Myriad
success.
Over the weekend, I took the time to run Elastic Search on Yarn using the
es-yarn package that elastic search has. This is a beta package, and
s
