[
https://issues.apache.org/jira/browse/AMBARI-12323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619314#comment-14619314
]
Hudson commented on AMBARI-12323:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #3078 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3078/])
AMBARI-12323. Ambari Dashboard HDFS - JMX metrics missing. (swagle) (swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1c7f70f8fc25b42e46470be7060f72ee310eb289)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
> Ambari Dashboard HDFS - JMX metrics missing
> -------------------------------------------
>
> Key: AMBARI-12323
> URL: https://issues.apache.org/jira/browse/AMBARI-12323
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Siddharth Wagle
> Priority: Critical
> Fix For: 2.1.0
>
>
> HDFS JMX dashboard metrics are missing.
> Ambari is using wrong port due to HA properties that contain nameserviceId.
> Default Ambari deploys contains old properties as well as new, so this Bug
> was not found in a non blueprint based HA deploys.
> Workaround: Add the following property to hdfs-site in the blueprint:
> "dfs.namenode.http-address" : <namenode-hostname>:<http-port>
> It doesn't matter which NN is used above since UI will get response with both
> JMX properties and choose Active one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
