[
https://issues.apache.org/jira/browse/HADOOP-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14480924#comment-14480924
]
Akira AJISAKA commented on HADOOP-11364:
----------------------------------------
I just hit this issue.
{code}
15/04/06 04:14:47 INFO mapreduce.Job: Task Id :
attempt_1428293579539_0001_m_000003_0, Status : FAILED
Container [pid=7847,containerID=container_1428293579539_0001_01_000005] is
running beyond virtual memory limits. Current usage: 123.5 MB of 1 GB physical
memory used; 2.6 GB of 2.1 GB virtual memory used. Killing container.
{code}
* Change yarn.nodemanager.vmem-pmem-ratio to some higher value (4 or 5?)
* Turn yarn.nodemanager.vmem-check-enabled to false
Either way is fine for me.
> [Java 8] Over usage of virtual memory
> -------------------------------------
>
> Key: HADOOP-11364
> URL: https://issues.apache.org/jira/browse/HADOOP-11364
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Mohammad Kamrul Islam
> Assignee: Mohammad Kamrul Islam
>
> In our Hadoop 2 + Java8 effort , we found few jobs are being Killed by Hadoop
> due to excessive virtual memory allocation. Although the physical memory
> usage is low.
> The most common error message is "Container [pid=??,containerID=container_??]
> is running beyond virtual memory limits. Current usage: 365.1 MB of 1 GB
> physical memory used; 3.2 GB of 2.1 GB virtual memory used. Killing
> container."
> We see this problem for MR job as well as in spark driver/executor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
