[
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094579#comment-14094579
]
Andrey Stepachev commented on HBASE-11467:
------------------------------------------
[~mantonov], great work!
How about using some ClusterIdProvider which will have a couple
implementations. Even so, it is not bad to have zk for configuration proposes,
if it already exists in infrastructure. So as a result we can make a bunch of
such providers and address them by some human readable cluster name.
As a sketch, lets uri will look like this:
zk://zk.host1:port,zk.host2:port,zk.host3:port/mycluster
If such uri will be configured on both, server and client, server will be able
to write all needed data into zk.
Alternatively uri conf://mycluster can be provided, and in that case all
configuration can be read from config (it can be some property names scheme to
find out masters and such)
> New impl of Registry interface not using ZK + new RPCs on master protocol
> -------------------------------------------------------------------------
>
> Key: HBASE-11467
> URL: https://issues.apache.org/jira/browse/HBASE-11467
> Project: HBase
> Issue Type: Sub-task
> Components: Client, Consensus, Zookeeper
> Affects Versions: 2.0.0
> Reporter: Mikhail Antonov
> Assignee: Mikhail Antonov
> Fix For: 2.0.0
>
> Attachments: HBASE-11467.patch, HBASE-11467.patch
>
>
> Currently there' only one implementation of Registry interface, which is
> using ZK to get info about meta. Need to create implementation which will be
> using RPC calls to master the client is connected to.
> Review of early version of patch is here: https://reviews.apache.org/r/24296/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
