[
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.003.patch
Thanks for the comment, [~xgong] and [~vinodkv]. I rebased the patch and made
java opts configurable. I used 256MB as the default value of max heap size.
> 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
> Assignee: Masatake Iwasaki
> Attachments: YARN-1912-0.patch, YARN-1912-1.patch, YARN-1912.003.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.3.4#6332)
