[
https://issues.apache.org/jira/browse/HBASE-20147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407557#comment-16407557
]
Hadoop QA commented on HBASE-20147:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 20s{color}
| {color:red} HBASE-20147 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-20147 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12915438/HBASE-20147-v6.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12052/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> 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
>
> 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.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)
