[
https://issues.apache.org/jira/browse/AMBARI-19573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827462#comment-15827462
]
Hadoop QA commented on AMBARI-19573:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847965/AMBARI-19573.v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10116//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10116//console
This message is automatically generated.
> Increase max limit for -Xmn parameter
> -------------------------------------
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
> Affects Versions: 2.5.0
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.5.0
>
> Attachments: AMBARI-19573.v3.patch, AMBARI-19573.v4.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
