You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2018/04/23 13:52:00 UTC

[jira] [Commented] (HBASE-20426) Give up replicating anything in S state

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

Duo Zhang commented on HBASE-20426:
-----------------------------------

A UT to represent the problem. Need HBASE-20456 in place before applying it.

> Give up replicating anything in S state
> ---------------------------------------
>
>                 Key: HBASE-20426
>                 URL: https://issues.apache.org/jira/browse/HBASE-20426
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Duo Zhang
>            Priority: Major
>         Attachments: HBASE-20426-UT.patch
>
>
> When we transit the remote S cluster to DA, and then transit the old A cluster to S, it is possible that we still have some entries which have not been replicated yet for the old A cluster, and then the async replication will be blocked.
> And this may also lead to data inconsistency after we transit it to DA back later as these entries will be replicated again, but the new data which are replicated from the remote cluster will not be replicated back, which introduce a whole in the replication.



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