[
https://issues.apache.org/jira/browse/YARN-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436224#comment-16436224
]
Hudson commented on YARN-7936:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13987 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13987/])
YARN-7936. Add default service AM Xmx. Contributed by Jian He (billie: rev
53b3e594732e7a567dda4e08b9a8af5f87a4472a)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/client/ServiceClient.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/conf/YarnServiceConf.java
> Add default service AM Xmx
> --------------------------
>
> Key: YARN-7936
> URL: https://issues.apache.org/jira/browse/YARN-7936
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jian He
> Assignee: Jian He
> Priority: Major
> Attachments: YARN-7936.1.patch
>
>
> We were seeing issues in the Service AM where memory usage would go beyond
> 1gb and AM container would get killed due to pmem check. We were not setting
> Xmx explicitly and hence it was getting defaulted to 32gb (based on the java
> version we were using and the available memory in the host). Hence even minor
> GC cycles were not kicking in and taking the usage beyond 1gb.
> We need to default Xmx to a reasonable value, ofcourse allowing it to be
> overridden by the service owner.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
