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

Duo Zhang commented on HBASE-19782:
-----------------------------------

When replaying remote WAL I think we will use ReplicationSink directly? And for 
the replication request from remote cluster, it will go through RSRpcService? 
Can we move the reject check into RSRpcService?

> Reject the replication request when peer is DA or A state
> ---------------------------------------------------------
>
>                 Key: HBASE-19782
>                 URL: https://issues.apache.org/jira/browse/HBASE-19782
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-19064-HBASE-19782.v1.patch, 
> HBASE-19064-HBASE-19782.v2.patch, HBASE-19782.HBASE-19064.v2.patch, 
> HBASE-19782.HBASE-19064.v2.patch, HBASE-19782.HBASE-19064.v3.patch, 
> HBASE-19782.HBASE-19064.v4.patch, HBASE-19782.HBASE-19064.v4.patch, 
> HBASE-19782.HBASE-19064.v4.patch, HBASE-19782.HBASE-19064.v5.patch, 
> HBASE-19782.HBASE-19064.v5.patch, HBASE-19782.HBASE-19064.v6.patch
>
>
> According to the design doc,  we'll initialize  both of the cluster state to 
> DA  after added the bidirectional  replication path.   and when a cluster in 
> DA state, it'll reject replication request.   
> so for cluster A and B in state DA,  if any received replication entry whose 
> table or namespace match the peer,    the cluster will  skip to apply into 
> its local rs.  



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

Reply via email to