[
https://issues.apache.org/jira/browse/AMBARI-21893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159681#comment-16159681
]
Hadoop QA commented on AMBARI-21893:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12885625/AMBARI-21893.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12165//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12165//console
This message is automatically generated.
> 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)
