[
https://issues.apache.org/jira/browse/AMBARI-12784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699459#comment-14699459
]
Hadoop QA commented on AMBARI-12784:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750784/AMBARI-12784.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 patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.AmbariManagementControllerTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3593//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3593//console
This message is automatically generated.
> RU: HS2 fails to start with invalid maximum heap size
> -----------------------------------------------------
>
> Key: AMBARI-12784
> URL: https://issues.apache.org/jira/browse/AMBARI-12784
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.1.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-12784.patch
>
>
> After upgrading from Ambari 1.7 to Ambari 2.1 and HDP 2.2.0 to HDP 2.3, Hive
> fails to start after upgrade during rolling upgrade due to hive-env.sh having
> HADOOP_HEAPSIZE=512*m*. The HADOOP_CLIENT_OPTS assumes it’s an int and tacts
> on an additional “m” so it ends up setting the -Xmx to 512mm instead of -Xmx
> to 512m
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)