[
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066969#comment-14066969
]
Mikhail Antonov commented on HBASE-11467:
-----------------------------------------
[~ghelmling] Thanks! Provided that each client has list of masters it
round-robin's across, that's probably the best option so far. I think I'm going
to stick with you suggestion.
As I look at the registry interface, this one call is the only one which is
hard to route thru the RPC, the others (getMetaRegionLocation,
isTableOnlineState, getCurrentNrHRS) would go thru RPC once the connection is
established.
> 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
> Assignee: 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)
