[
https://issues.apache.org/jira/browse/AMBARI-21893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164092#comment-16164092
]
Hudson commented on AMBARI-21893:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #202 (See
[https://builds.apache.org/job/Ambari-branch-2.6/202/])
Revert "AMBARI-21893 : NameNode Heap Usage (Daily) metric alert status
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c69b750bde1c6964bda4894898d28495c6370221])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-ssl-client.xml
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java
> 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)
