You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2013/11/15 20:15:22 UTC

[jira] [Reopened] (AMBARI-3775) Adding or Deleting zookeeper servers should reconfigure ha.zookeeper.quorum, hbase.zookeeper.quorum, and templeton.zookeeper.hosts properties

     [ https://issues.apache.org/jira/browse/AMBARI-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yusaku Sako reopened AMBARI-3775:
---------------------------------


> Adding or Deleting zookeeper servers should reconfigure ha.zookeeper.quorum, hbase.zookeeper.quorum, and templeton.zookeeper.hosts  properties
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3775
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3775
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3775.patch
>
>
> * Adding or Deleting ZooKeeper servers should reconfigure ha.zookeeper.quorum in core-site.xml if NameNode HA is enabled, hbase.zookeeper.quorum if HBase is installed, and templeton.zookeeper.hosts if WebHcat is installed.
>  * Right now we set above properties automatically in web-ui when we reconfigure the respective service for the first time after deleting or introducing new zookeeper server in the cluster.
> * We should explicitly do the reconfiguration while adding or deleting action is done on zookeeper server.
> * if we had to surface the properties on service configuration page, We should  also display the message while adding or removing ZooKeeper server that this action will reconfigure above properties.



--
This message was sent by Atlassian JIRA
(v6.1#6144)