[jira] [Commented] (HBASE-11392) Replication requests should be routed through master

["Guanghao Zhang (JIRA)" <ji...@apache.org>]

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

Guanghao Zhang commented on HBASE-11392:
----------------------------------------

[~talat] Are you still work on this? If not, I can pick up this issue. And I thought we can make this issue as a umbrella issue and divide it to some small issues.
1. add/remove peer requests are routed through master
2. enable/disable peer requests are routed through master
3. get/update peer config requests are routed through master
4. list peers requests are routed through master
5. Use nonce for non-idempotent operations
6. Use Procedure V2
7. Remove the unused code and move replication classes to hbase-server

Any ideas? [~enis]

> Replication 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: Talat UYARER
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)