[jira] [Updated] (AMBARI-15880) ATS heapsize cannot be changed in Ambari-2.2.1.1 or greater post Ambari Server upgrade, even though the bug should be fixed

["Andrew Onischuk (JIRA)" <ji...@apache.org>]

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

Andrew Onischuk updated AMBARI-15880:
-------------------------------------
    Attachment: AMBARI-15880.patch

> ATS heapsize cannot be changed in Ambari-2.2.1.1 or greater post Ambari Server upgrade, even though the bug should be fixed
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15880
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15880
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15880.patch
>
>
> yarn-env had an issue where ATS heapsize was not getting set correctly
> This was fixed in Ambari-2.1.0 for HDP 2.2 and Ambari-2.2.1.1 for HDP 2.3/2.4.  
> However, "ambari-server upgrade" does not fix yarn-env, even if the user has
> never touched it.
> STR:
>   * Install a HDP 2.4.0 cluster with YARN using Ambari 2.2.1.0
>   * Confirm that yarn-env has **export YARN_HISTORYSERVER_HEAPSIZE=`apptimelineserver_heapsize`** (this is incorrect)
>   * ambari-server stop
>   * Install ambari.repo for Ambari 2.2.1.1
>   * yum upgrade ambari-server
>   * ambari-server upgrade
>   * ambari-server start
> Actual: yarn-env still has **export
> YARN_HISTORYSERVER_HEAPSIZE=`apptimelineserver_heapsize`**  
> Expected: yarn-env has **export
> YARN_TIMELINESERVER_HEAPSIZE=`apptimelineserver_heapsize`** instead
> This means that changing "AppTimelineServer Java heap size" from the UI has no
> effect on setting the actual heapsize for ATS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)