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

Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2017/04/21 12:07:04 UTC

[jira] [Updated] (AMBARI-20747) Upgrade is not taking care of AMBARI-15677

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

Jonathan Hurley updated AMBARI-20747:
-------------------------------------
    Status: Patch Available  (was: Open)

> Upgrade is not taking care of AMBARI-15677
> ------------------------------------------
>
>                 Key: AMBARI-20747
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20747
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.1
>            Reporter: amarnathreddy
>            Assignee: Jonathan Hurley
>            Priority: Critical
>
> When customer upgraded their Ambari from 2.2.1 to 2.4.1 and HDP 2.3.4 to 2.5.3 
> it is not taking care of   https://issues.apache.org/jira/browse/AMBARI-15677 RESOLVED  bug.
> Ambari does not set -XX:CMSInitiatingOccupancyFraction=70 or -XX:+UseCMSInitiatingOccupancyOnly properties.
> where as fresh install comes up with these parameters. this needs to be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)