Jan,
As part of YARN-1011 (oversubscription work), we are looking at better
(faster) ways of monitoring and enforcement and considering putting all
YARN containers under a cgroup with hard limit so YARN as a whole does not
go over a limit, but let the individual containers run over. The details
Hi Ravi,
sorry for late answer. :) We are on hadoop 2.6-cdh5.7.
Cheers,
Jan
On 12.8.2016 01:57, Ravi Prakash wrote:
Hi Jan!
Yes! Makes sense. I'm sure there were bigger changes for the
ResourceHandler. Which version are you on?
Cheers
Ravi
On Thu, Aug 11, 2016 at 7:48 AM, Jan Lukavský
Hi Jan!
Yes! Makes sense. I'm sure there were bigger changes for the
ResourceHandler. Which version are you on?
Cheers
Ravi
On Thu, Aug 11, 2016 at 7:48 AM, Jan Lukavský
wrote:
> Hi Ravi,
>
> I don't think cgroups will help us, because, we don't want to impose a
Hi Ravi,
I don't think cgroups will help us, because, we don't want to impose a
hard limit on the memory usage, we just want to allow for short time
periods, when container can consume more memory than its limit. We don't
want to put the limit too high, because that causes underutilization of
Hi Jan!
Thanks for your explanation. I'm glad that works for you! :-)
https://issues.apache.org/jira/browse/YARN-5202 is something that Yahoo!
talked about at the Hadoop Summit, (and it seems the community may be going
in a similar direction, although not exactly the same.) There's also
Hi Ravi,
we don't run into situation where memory used > RAM, because memory
configured to be used by all containers on a node is less than the total
amount on memory (by a factor of say 10%). The spikes of container
memory usage, that are tolerated due to the averaging don't happen on
all
Hi Jan!
Thanks for your contribution. In your approach what happens when a few
containers on a node are using "excessive" memory (so that total memory
used > RAM available on the machine). Do you have overcommit enabled?
Thanks
Ravi
On Tue, Aug 9, 2016 at 1:31 AM, Jan Lukavský
Hello community,
I have a question about container resource calculation in nodemanager.
Some time ago a filed JIRA
https://issues.apache.org/jira/browse/YARN-4681, which I though might
address our problems with container being killed because of read-only
mmaping memory block. The JIRA has