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

Posted to yarn-issues@hadoop.apache.org by "Masatake Iwasaki (JIRA)" <ji...@apache.org> on 2014/04/23 22:44:23 UTC

[jira] [Updated] (YARN-1912) ResourceLocalizer started without any jvm memory control

     [ https://issues.apache.org/jira/browse/YARN-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Masatake Iwasaki updated YARN-1912:
-----------------------------------

    Attachment: YARN-1912-0.patch

attaching patch adding JVM option to ContainerLocalizer.

> 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
>         Attachments: YARN-1912-0.patch
>
>
> 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
(v6.2#6252)