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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/05/02 06:56:07 UTC
[jira] [Commented] (YARN-1912) ResourceLocalizer started without
any jvm memory control
[ 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)