[
https://issues.apache.org/jira/browse/AMBARI-12784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699700#comment-14699700
]
Hudson commented on AMBARI-12784:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3281 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3281/])
AMBARI-12784 RU: HS2 fails to start with invalid maximum heap size (dsen)
(dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=baed7e987ce5ad1628120655d6de33bf314bf08b)
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
> 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)
