[
https://issues.apache.org/jira/browse/HBASE-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811728#comment-13811728
]
Eric Yang commented on HBASE-4072:
----------------------------------
Would it be better to have a single place of truth for maintaining
configuration? With ZooKeeper 3.5, if the zookeeper quorum has new zookeeper
node join the cluster, instead of modify zookeeper server config, hbase
master/region server, and hbase client configuration, hdfs QJM namenode
configuration. Would it be better to keep it in zoo.cfg which can be loaded
into any java program's classpath? It seems it is less troublesome to maintain
a global copy than multiple localized copies.
> Deprecate/disable and remove support for reading ZooKeeper zoo.cfg files from
> the classpath
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-4072
> URL: https://issues.apache.org/jira/browse/HBASE-4072
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.0
> Reporter: stack
> Assignee: Harsh J
> Fix For: 0.95.0
>
> Attachments: HBASE-4072.patch, HBASE-4072.patch, HBASE-4072.patch
>
>
> This issue was found by Lars:
> http://search-hadoop.com/m/n04sthNcji2/zoo.cfg+vs+hbase-site.xml&subj=Re+zoo+cfg+vs+hbase+site+xml
> Lets fix the inconsistency found and fix the places where we use non-zk
> attribute name for a zk attribute in hbase (There's only a few places that I
> remember -- maximum client connections is one IIRC)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
