Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 18 Sep 2015 19:11:05 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12760300.1418081224000.15243.1442603465600@Atlassian.JIRA>
In-Reply-To: <JIRA.12760300.1418081224000@Atlassian.JIRA>
References: <JIRA.12760300.1418081224000@Atlassian.JIRA>
 <JIRA.12760300.1418081224857@arcas>
Subject: [jira] [Commented] (HADOOP-11364) [Java 8] Over usage of virtual
 memory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran commented on HADOOP-11364:
-----------------------------------------

set in yarn-site and read by the resource manager: it's a cluster-wide policy.

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