hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4714) [Java 8] Over usage of virtual memory
Date Mon, 22 Feb 2016 10:46:18 GMT

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

Steve Loughran commented on YARN-4714:

true, but it's still traumatic: cluster performance can seriously suffer. I also expect management
tools & their hadoop installations to restore the 2.6 value. Changing the ratio is the
solution that would be viable in production with vmem checks enabled

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

View raw message