[jira] [Commented] (HBASE-20147) Serial replication will be stuck if we create a table with serial replication but add it to a peer after there are region moves

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

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

Hudson commented on HBASE-20147:
--------------------------------

Results for branch branch-2
	[build #590 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/590/]: (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/branch-2/590//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/590//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/590//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


> Serial replication will be stuck if we create a table with serial replication but add it to a peer after there are region moves
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20147
>                 URL: https://issues.apache.org/jira/browse/HBASE-20147
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.1.0
>
>         Attachments: HBASE-20147-v1.patch, HBASE-20147-v2.patch, HBASE-20147-v3.patch, HBASE-20147-v4.patch, HBASE-20147-v5.patch, HBASE-20147-v6.patch, HBASE-20147-v7.patch, HBASE-20147-v8.patch, HBASE-20147.patch, HBASE-20147.patch
>
>
> The start point for serial replication is that, if we are in the first range then we are safe to push. And we will record replication barrier when the replication scope is set to SERIAL even if the table is not contained in any peers. So it could happen that, we record several barriers in the meta already and then we add a peer which contains this table. So when replicating, we will find that we are not in the first range, and then the replication will be stuck.



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