hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1912) ResourceLocalizer started without any jvm memory control
Date Sat, 02 May 2015 04:56:07 GMT

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

Hadoop QA commented on YARN-1912:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply the patch during
dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12642478/YARN-1912-1.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7626/console |


This message was 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)

Mime
View raw message