[
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094704#comment-14094704
]
ryan rawson commented on HBASE-11467:
-------------------------------------
Having an extra RPC to figure out who you're talking to isn't horrifyingly bad.
Thinking broader, how does SSH do this? Could we emulate that? I believe that
in SSH you can tell it via config that this key should be used for this
host(s), and absent that, it walks thru the set of keys it has at its disposal.
What is the simplest approach for the user? Magic strings tend to be not liked
much
> 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)
