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

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

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

Hudson commented on HBASE-20426:
--------------------------------

Results for branch master
	[build #380 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/380/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/380//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/380//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/380//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> 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
>          Components: Replication
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-20426-HBASE-19064-v1.patch, HBASE-20426-HBASE-19064-v1.patch, HBASE-20426-HBASE-19064-v1.patch, HBASE-20426-HBASE-19064-v1.patch, HBASE-20426-HBASE-19064-v1.patch, HBASE-20426-HBASE-19064-v2.patch, HBASE-20426-HBASE-19064-v3.patch, HBASE-20426-HBASE-19064-v4.patch, HBASE-20426-HBASE-19064.patch, HBASE-20426-HBASE-19064.patch, HBASE-20426-HBASE-19064.patch, 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)