[jira] [Updated] (AMBARI-21893) NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN intermittently when AMS HTTPS is enabled.

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

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

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

> NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN intermittently when AMS HTTPS is enabled.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21893
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21893
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.6.0
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21893.patch
>
>
> Underlying Issue
> This issue is because of AMS HTTPS + HA scenario. The CA cert file (/etc/ambari-metrics-monitor/conf/ca.pem) found on every host is generated by fetching a specific metric collector host's certificate from the truststore.
> This certificate file is being used by alert script, service check and even monitors to talk to collector.
> * For example, in a cluster with hosts H1 to H5, let's say there are 2 collectors - H1 & H2.
> * On a node H3, let's say the ca.pem file was constructed using the certificate for collector H2.
> * Service check or metric monitor on H3 will NOT be able to talk to H1 since it does not have the certificate for that host.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)