ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-14108) AMS Collector does not start with 2.1.2 input and env scripts
Date Sun, 29 Nov 2015 02:48:10 GMT

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

Aravindan Vijayan updated AMBARI-14108:
---------------------------------------
    Attachment: AMBARI-14108.patch

> AMS Collector does not start with 2.1.2 input and env scripts
> -------------------------------------------------------------
>
>                 Key: AMBARI-14108
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14108
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.1.3
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-14108.patch
>
>
> PROBLEM
> Ams collector does not startup because of ams-env.sh issues.
> BUG
> When the "metrics_collector_heapsize" property in ams-env is given a value of "512m"
using blueprints, we do not trim the "m" suffix. The ams-env content template adds another
"m" causing the startup to fail.
> FIX
> Added the trimming logic of ams hbase heapsize properties to metrics_collector_heapsize
property as well.



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

Mime
View raw message