hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11467) New impl of Registry interface not using ZK + new RPCs on master protocol
Date Sun, 31 Aug 2014 07:55:53 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116663#comment-14116663

Mikhail Antonov commented on HBASE-11467:

[~stack] may be to bring back here in jira the conversation started on RB..

So.. in the context of discussion happening in 'scaling to 1M regions" jira - how would you
suggest to proceed with this patch? I addressed most of the comments from review board (thanks
for reviews!), and incorporated with feedbacks from [~ryanobjc] above, and working on fixing
and reworking tests (some failures aren't related, but some are caused by certain changes
in minicluster infrastructure). Do you think it may be 'committable' by itself, of it should
be on-hold until further steps on cluster topology discussion? Would appreciate your thoughts
on that.

> 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

View raw message