hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guanghao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-11392) add/remove peer requests should be routed through master
Date Sat, 24 Dec 2016 05:15:58 GMT

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

Guanghao Zhang updated HBASE-11392:
    Release Note: Add/Remove replication peer requests will be routed through master.

> 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
>            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

View raw message