You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/08/17 12:10:45 UTC

[jira] [Updated] (AMBARI-12784) RU: HS2 fails to start with invalid maximum heap size

     [ https://issues.apache.org/jira/browse/AMBARI-12784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen updated AMBARI-12784:
--------------------------------
    Attachment: AMBARI-12784.patch

> 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)