[
https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416706#comment-16416706
]
Hudson commented on HBASE-20138:
--------------------------------
Results for branch HBASE-19064
[build #77 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//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/HBASE-19064/77//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/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Find a way to deal with the conflicts when updating replication position
> ------------------------------------------------------------------------
>
> Key: HBASE-20138
> URL: https://issues.apache.org/jira/browse/HBASE-20138
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Zheng Hu
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch,
> HBASE-20138.v3.patch, HBASE-20138.v4.patch, HBASE-20138.v5.patch,
> HBASE-20138.v6.patch, HBASE-20138.v7.patch
>
>
> For now if a table is not created with SERIAL_REPLICATION_SCOPE and later
> converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication
> sources which replicate the different ranges for the same region and update
> the queue storage concurrently. This will cause problem if the lower range
> finish at last since the replication position will be wrong...
> Need to find a way to deal with this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)