hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yitong Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11364) [Java 8] Over usage of virtual memory
Date Fri, 18 Sep 2015 03:38:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804916#comment-14804916

Yitong Zhou commented on HADOOP-11364:

Is yarn.nodemanager.vmem-pmem-ratio and yarn.nodemanager.vmem-check-enabled are only supposed
to be effective when set in yarn-site.xml or before a container is launched? I tried to set
it via JobConf, and did not see an effect. Mohammad's suggestion tweaking jvm.opts worked

> [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

View raw message