You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Tsuyoshi Ozawa (JIRA)" <ji...@apache.org> on 2016/02/16 09:43:18 UTC

[jira] [Commented] (HADOOP-11364) [Java 8] Over usage of virtual memory

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

Tsuyoshi Ozawa commented on HADOOP-11364:
-----------------------------------------

[~ajisakaa] I don't think the workaround, turning vmem-check off, is acceptable. It's incompatible change as described on YARN-2225.

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