hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stanley shi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1912) ResourceLocalizer started without any jvm memory control
Date Wed, 09 Apr 2014 04:25:15 GMT

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

stanley shi commented on YARN-1912:

No, it's not the minumum. On one of my environment which has 32GB mem:
/opt/jdk1.7.0_15/bin/java -XX:+PrintFlagsFinal -version 2>&1 | grep MaxHeapSize
    uintx MaxHeapSize                              := 8415870976      {product}
And also some answer from oracle: 

{quote}Server JVM heap configuration ergonomics are now the same as the Client, except that
the default maximum heap size for 32-bit JVMs is 1 gigabyte, corresponding to a physical memory
size of 4 gigabytes, and for 64-bit JVMs is 32 gigabytes, corresponding to a physical memory
size of 128 gigabytes.

> ResourceLocalizer started without any jvm memory control
> --------------------------------------------------------
>                 Key: YARN-1912
>                 URL: https://issues.apache.org/jira/browse/YARN-1912
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.2.0
>            Reporter: stanley shi
> In the LinuxContainerExecutor.java#startLocalizer, it does not specify any "-Xmx" configurations
in the command, this caused the ResourceLocalizer to be started with default memory setting.
> In an server-level hardware, it will use 25% of the system memory as the max heap size,
this will cause memory issue in some cases.

This message was sent by Atlassian JIRA

View raw message