Problem description
Container [pid=3962,containerID=container_1632883011739_0002_01_000002] is running 270113280B beyond the ‘VIRTUAL’ memory limit.
Current usage: 91.9 MB of 1 GB physical memory used; 2.4 GB of 2.1 GB virtual memory used. Killing container.
Cause of problem
When yarn starts running, it checks the virtual memory and throws an exception.
Solution:
Modify Hadoop_Home/etc/Hadoop/yen-site.xml file
Add the following to save and exit:
1 <property> 2 <name>yarn.nodemanager.vmem-pmem-ratio</name> 3 <value>3.0</value> 4 </property>
Problem solved!
Similar Posts:
- [Solved] CDH6.3.2 Hive on spark Error: is running beyond physical memory limits
- Tuning and setting of memory and CPU on yarn cluster
- The key technologies in hadoop-3.0.0 configuration yarn.nodemanager.aux -Services item
- Error: Could not find or load main class org.apache.hadoop.mapreduce.v2.app.MRAppMaster
- [Solved] /bin/bash: /us/rbin/jdk1.8.0/bin/java: No such file or directory
- Spark2.x Error: Queue’s AM resource limit exceeded.
- YARN Restart Issue: RM Restart/RM HA/Timeline Server/NM Restart
- [Solved] Hadoop Error: The directory item limit is exceeded: limit=1048576 items=1048576
- [Solved] Hadoop Error: ERROR: Attempting to operate on yarn resourcemanager as root