[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404594#comment-16404594 ]
Duo Zhang commented on HBASE-20138: ----------------------------------- {quote} If only allow the rs which has the region online currently to update the region's last pushed sequence id, so no conflicts will happen ? {quote} This does not work. The rs which has the region online may be blocked because of the previous range has not been finished yet... > 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 > Reporter: Duo Zhang > Assignee: Zheng Hu > Priority: Major > > 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)