[jira] [Commented] (AMBARI-5217) Incorrect Stale Config indicator shown for HDFS, YARN and MR2 service after adding Zookeeper server to a host.

["Jaimin D Jetly (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947393#comment-13947393 ] 

Jaimin D Jetly commented on AMBARI-5217:
----------------------------------------

review available at https://reviews.apache.org/r/19658/

> Incorrect Stale Config indicator shown for HDFS, YARN and MR2 service after adding Zookeeper server to a host.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-5217
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5217
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 1.5.1
>
>         Attachments: AMBARI-5217.patch
>
>
>  Adding zookeeper component to a host in namenode HA enabled cluster  requires reconfiguring ha.zookeeper.quorum property. Over here showing stale config indicator for HDFS, YARN and MR2 services is expected behavior. But When NameNode HA is not enabled, web client should not reconfigure core-site as none of the config has actually changed and still web ui shows stale config for the core hadoop services. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)