[
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094755#comment-14094755
]
Mikhail Antonov commented on HBASE-11467:
-----------------------------------------
[~ghelmling] thanks for clarification!
One thing which comes to my mind - imagine we have ZK string, or masters quorum
string, as a cluster id. It's in format of host1:port1,host2:port2,hostN:portN.
Presumably it doesn't change that often. And it's used as a selector, or key,
to lookup token associated with this entity (cluster). It doesn't really have
to be canonical, perhaps.
On the very first connection, if there's no token, we fall back to GSSAPI, and
when we have token, we use DIGEST-MD5. So in the scenario of masters connection
string, of zk quorum string, we use it as a token selector. If at some point
masters membership changes, and client needs to update his local quorum string
- then the consequence will be that cached token may not longer be looked up
using new connection string, so new GSSAPI pass will have to happen. Is that
bad?
> 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)
