You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Krishna Chaitanya (JIRA)" <ji...@apache.org> on 2016/07/26 04:45:21 UTC
[jira] [Commented] (YARN-4714) [Java 8] Over usage of virtual
memory
[ https://issues.apache.org/jira/browse/YARN-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393214#comment-15393214 ]
Krishna Chaitanya commented on YARN-4714:
-----------------------------------------
Same issue with jdk1.8.0_60. By changing "yarn.nodemanager.vmem-pmem-ratio to some higher value (4 )" and Turn "yarn.nodemanager.vmem-check-enabled to false" no effect on container kills. With jdk1.7.0_67 no issues.
> [Java 8] Over usage of virtual memory
> -------------------------------------
>
> Key: YARN-4714
> URL: https://issues.apache.org/jira/browse/YARN-4714
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Mohammad Kamrul Islam
> Assignee: Mohammad Kamrul Islam
> Priority: Blocker
> Attachments: HADOOP-11364.01.patch
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org