Hi,
Brilliant! Working now.
Thank you very much,
On 05/06/16 18:09, Darin Johnson wrote:
> Stephen,
>
> I was able to recreate the problem (specific due to 2.7.2, they changed the
> defaults on the following two properties to true). Setting them to false
> allowed me to again run map reduce
Stephen,
I was able to recreate the problem (specific due to 2.7.2, they changed the
defaults on the following two properties to true). Setting them to false
allowed me to again run map reduce jobs. I'll try to update the
documentation later today.
yarn.nodemanager.pmem-check-enabled
Some in line commentary. I've also included in the to podlings I've made
comments on.
On Sun, Jun 5, 2016 at 10:11 AM John D. Ament wrote:
> All,
>
> Please find the current draft of the board report below. Its still
> missing sign off from mentors on several projects.
Hey Stephen,
I think you're pretty close.
Looking at the config I'd suggest removing these properties:
yarn.nodemanager.resource.memory-mb
4096
yarn.scheduler.maximum-allocation-vcores
12
yarn.scheduler.maximum-allocation-mb
Hi,
Attached. Thanks very much for looking.
Cheers,
On 05/06/16 12:51, Darin Johnson wrote:
> Hey Steven can you please send your yarn-site.xml, I'm guessing you're on
> the right track.
>
> Darin
> Hi,
>
> OK. That helps, thank you. I think I just misunderstood the docs (or
> they never
Hi,
OK. That helps, thank you. I think I just misunderstood the docs (or
they never said explicitly that you did need at least some static
resource), and I scaled down the initial nm.medium that got started. I
get a bit further now, and jobs start but are killed with:
Diagnostics: