You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2019/05/14 00:41:00 UTC

[jira] [Updated] (HBASE-11392) add/remove peer requests should be routed through master

     [ https://issues.apache.org/jira/browse/HBASE-11392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Biju Nair updated HBASE-11392:
------------------------------
    Component/s: Replication

> add/remove peer requests should be routed through master
> --------------------------------------------------------
>
>                 Key: HBASE-11392
>                 URL: https://issues.apache.org/jira/browse/HBASE-11392
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: Enis Soztutar
>            Assignee: Guanghao Zhang
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: HBASE-11392-v1.patch, HBASE-11392-v2.patch, HBASE-11392-v3.patch, HBASE-11392-v4.patch, HBASE-11392-v5.patch, HBASE-11392-v6.patch
>
>
> ReplicationAdmin directly operates over the zookeeper data for replication setup. We should move these operations to be routed through master for two reasons: 
>  - Replication implementation details are exposed to client. We should move most of the replication related classes to hbase-server package. 
>  - Routing the requests through master is the standard practice for all other operations. It allows for decoupling implementation details from the client and code.
> Review board: https://reviews.apache.org/r/54730/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)