hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masatake Iwasaki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1912) ResourceLocalizer started without any jvm memory control
Date Wed, 23 Apr 2014 17:51:16 GMT

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

Masatake Iwasaki commented on YARN-1912:

I think adding default -Xmx for safety is good though ContainerLocalizer which is forked from
LinuxContainerExecutor.java#startLocalizer does not do memory consuming work but just make
directories and download resource files for task.
(JVM allocate not maximum but minimum heap at startup without -Xms option, for note.)

> 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