FAQ
Hi,
CM will recommend heap sizes based on the RAM available on that host and
the other roles located on that host. The ideal heap size for NodeManager,
for instance, is 1GB. If there isn't enough RAM on the host to allocate
ideal heaps to all the roles, then the recommended heaps will be scaled
back up to a minimum of 50MB for that particular instance. That would
explain the overrides.

-Vinithra
On Tue, Aug 28, 2012 at 12:31 AM, Jon Ramos wrote:

Also, the NodeManager's Java Heap Size in bytes is set to 1073741824
bytes, which is 1 GB. But that is overridden by one instance to 88505430,
which is only 84 MB.

JobHistory server has a similar thing going on. 268435456 bytes is the
current setting, but that's overridden to 60058970 bytes or 57 MB.

Search Discussions

Discussion Posts

Previous

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 9 of 9 | next ›
Discussion Overview
groupscm-users @
categorieshadoop
postedAug 27, '12 at 7:03p
activeAug 28, '12 at 6:57p
posts9
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase