[
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057909#comment-14057909
]
Mikhail Antonov commented on HBASE-11467:
-----------------------------------------
Thanks for comment [~ghelmling] !
I see several possible options here.
- ClusterId is used in RpcClient code, in TokenSelector.selectToken(..). Since
cluster id is publicly available information. We could use something else for
token here, like hbase.masters.quorum property, containing list of active
masters?
- ClusterId is a tag used to identity cluster. Does it make sense to have it
also on the client side in hbase-conf.xml? If it doesn't match the id stored in
the cluster, then client can't connect?
- ClusterId is also stored in HDFS in hdfs:/<namenode>:<port>/hbase/hbase.id.
Clients who have connection to HDFS could read it from there. Several drawbacks
- clients may not have access to HDFS at all, also this is implementation
detail which we shall not disclose to clients.
> 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
> Reporter: Mikhail Antonov
> Fix For: 2.0.0
>
>
> 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.
> That includes adding several new methods to master RPC protocol:
> - GetMetaRegionLocation
> - GetClusterId
> - IsTableOnlineState
> - GetCurrentNrHRS
--
This message was sent by Atlassian JIRA
(v6.2#6252)
