[
https://issues.apache.org/jira/browse/AMBARI-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-14120:
---------------------------------------
Attachment: AMBARI-14120.patch
> AMS Collector and HBase heap memory config properties are incompatible
> between 2.1.2 and 2.1.3 when deployed through the same blueprint.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14120
> URL: https://issues.apache.org/jira/browse/AMBARI-14120
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.3
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14120.patch
>
>
> PROBLEM
> On Version 2.1.2, AMS had no "m" in the heap properties in the *-env.sh
> templates and the user was expected to specify the "m" suffix through the UI
> config.
> On Version 2.1.3, AMS had the "m" suffix in the heapsize properties in the
> *-env.sh templates, and the user was not allowed to give the "m" suffix in
> the UI.
> When a 2.1.2 blueprint is used to deploy Ambari 2.1.3, AMS does not start due
> to invalid heap properties.
> FIX
> The input heapsize parameter can either be 512 (UI) or 512m (blueprint). The
> "m" is added to the former case programmatically to achieve uniformity. The
> ams-hbase-content will not have "m" appended to any property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
