ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-9566) Ambari HDFS jmx give none/wrong status in https setup for hdfs and yarn, etc
Date Wed, 11 Feb 2015 14:59:12 GMT
Andrew Onischuk created AMBARI-9566:
---------------------------------------

             Summary: Ambari HDFS jmx give none/wrong status in https setup for hdfs and yarn,
etc
                 Key: AMBARI-9566
                 URL: https://issues.apache.org/jira/browse/AMBARI-9566
             Project: Ambari
          Issue Type: Bug
            Reporter: Andrew Onischuk
            Assignee: Andrew Onischuk
             Fix For: 2.0.0


PROBLEM:

HDP 2.2.0, Ambari 1.7.0.  
When enable namnode HA with https by dfs.http.policy=HTTPS_ONLY, and set up
required ssl-server.xml and ssl-client.xml, hdfs function fine.

But Ambari UI shows no metrics for namenode, even shows 'upgrade not
finalized' when it is a fresh HDP 2.2.0. install.

A few notes:  
1\. there is no option in 'ambari-server setup-security' or documentation on
how to set up trust store for Ambari to trust hdfs/yarn

2\. it looks like Ambari still uses hadoop.ssl.enabled as criteria whether
https is enabled. This is deprecated since hdp 2.1. The property should be
dfs.http.policy, yarn.http.policy.

screenshot attached that shows the wrong and missing metrics, and screenshot
of the jmx from namenode





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

Mime
View raw message