[jira] [Commented] (AMBARI-14108) AMS Collector does not start with 2.1.2 input and env scripts

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

    [ https://issues.apache.org/jira/browse/AMBARI-14108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031104#comment-15031104 ] 

Hudson commented on AMBARI-14108:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #959 (See [https://builds.apache.org/job/Ambari-branch-2.1/959/])
AMBARI-14108. AMS Collector does not start with 2.1.2 input and env (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9dc2e44f0ad60597f175c260f926b237d2a5d6b2])
* ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py


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