[
https://issues.apache.org/jira/browse/YARN-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536588#comment-14536588
]
Hudson commented on YARN-1912:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #180 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/180/])
YARN-1912. ResourceLocalizer started without any jvm memory control. (xgong:
rev 6471d18bc72bc6c83ce31a03b5c5f5737847bb6d)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* hadoop-yarn-project/CHANGES.txt
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/LinuxContainerExecutor.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestLinuxContainerExecutorWithMocks.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/ContainerLocalizer.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/WindowsSecureContainerExecutor.java
> 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
> Labels: BB2015-05-RFC
> Fix For: 2.8.0
>
> Attachments: YARN-1912-0.patch, YARN-1912-1.patch,
> YARN-1912.003.patch, YARN-1912.004.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)
