[
https://issues.apache.org/jira/browse/HADOOP-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239754#comment-14239754
]
Gera Shegalov commented on HADOOP-11364:
----------------------------------------
Hi [~kamrul], can you confirm that your settings of mapreduce.reduce.memory.mb
irrespective of Java8? "2.1 GB virtual memory used" is suspicious in a sense
that it looks {{vmem-pmem-ratio(2.1) * default
mapreduce.reduce.memory.mb(1024)}}. However, the reducer is declared to
allocate for Java heap -Xmx1536m , let alone the total virtual C-Heap of the
JVM.
> [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)
