[
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070075#comment-14070075
]
Mikhail Antonov commented on HBASE-11467:
-----------------------------------------
Looks like getting clusterId during HConnection initialization using REST call
to master isn't that straightforward solution, as master itself creates
hconneciton (for example when it creates StartupManager), and it happens well
before Jetty container is initialized for master. Even if we change the
sequence of steps for master initialization, making REST call from inside
master code to the web endpoint seems a bit strange.
So I guess the question is if we can make token selector use information which
can be obtained from local configuration instead? Like store clusterId in
client configuration (how often is it updated?), or may be use for example
masters.quorum.addresses instead, as cluster identifier?
> 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
> - IsTableOnlineState
> - GetCurrentNrHRS
> Additionally, new HTTP endpoint would be added to the master, so anyone can
> request ClusterId without any authentication.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
