[
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117891#comment-14117891
]
Mikhail Antonov commented on HBASE-11467:
-----------------------------------------
[~stack] not the latest one, in sense that I'm going to publish new version on
RB tonight or early this week, maybe tomorrow (mostly it's fixing the tests
with changes invariants/expectations of master being up/down). In new version,
this setRegistry() will go away. Found the way to get rid of it.
At the high level - totally agree that it's change is a radical one, I targeted
it for 2.0 for now. I'll start the discussion in the mail list, too. On the
side note - this patch itself doesn't change the way how the servers themselves
(HMs or HRSs) are talking to each other, so _master-based cluster_ isn't what's
coming with this patch.
Do you suggest to put this patch on hold, or modify it so it's more like
"second option to connect to cluster"?
> 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, 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.3.4#6332)
