[
https://issues.apache.org/jira/browse/YARN-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129812#comment-14129812
]
Hadoop QA commented on YARN-1912:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12642478/YARN-1912-1.patch
against trunk revision 4be9517.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4885//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4885//console
This message is automatically generated.
> 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, YARN-1912-1.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)
