hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rahul Chhiber <rahul.chhi...@cumulus-systems.com>
Subject Node Manager crashes with OutOfMemory error
Date Tue, 26 Jul 2016 06:05:40 GMT
Hi All,

I am running a Hadoop cluster with following configuration :-

Master (Resource Manager) - 16GB RAM + 8 vCPU
Slave 1 (Node manager 1) - 8GB RAM + 4 vCPU
Slave 2 (Node manager 2) - 8GB RAM + 4 vCPU

Memory allocated for container use per slave  i.e. yarn.nodemanager.resource.memory-mb is

When I launch an application, container allocation and execution is successful, but after
executing 1 or 2 jobs on the cluster, either one or both the node manager daemons crash with
the following error in logs :-

"java.lang.OutOfMemoryError: Java heap space
        at java.util.Arrays.copyOf(Arrays.java:2367)
        at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)
        at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)
        at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)
        at java.lang.StringBuffer.append(StringBuffer.java:237)
        at org.apache.hadoop.util.Shell$1.run(Shell.java:511)
2016-07-22 06:54:54,326 INFO org.apache.hadoop.util.ExitUtil: Halt with status -1 Message:

We have allocated 1 GB of heap space for each node manager daemon. On average there are about
3 containers running on 1 slave node. We have been running Hadoop clusters for a while now,
but haven't faced this issue until recently. What are the memory sizing recommendations for
Nodemanager ? As per my understanding, the memory used by containers or by the Application
master should not have any bearing on Node manager memory consumption, as they all run in
separate JVMs. What could be the possible reasons for high memory consumption for the Node

NOTE :- I tried allocating more heap memory for Node manager (2 GB), but issue still occurs
intermittently. Containers getting killed due to excess memory consumption is understandable
but if Node manager crashes in this manner it would be a serious scalability problem.

Rahul Chhiber

View raw message