[
https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407673#comment-16407673
]
Zheng Hu commented on HBASE-20138:
----------------------------------
But this introduce another problem if changing step.2, if region finished
step.3 and write nothing, then the rs crashed, and moved to another new RS, do
this many times. finally, there will be many logs with the same sequence id
(all of them are open region marker), if replication reached a seq id can
pushed, then all of those entries with same sequence id will try to push and
update the last pushed sequence id even if the peer has been serial ..
So a more safe way will be fixing the conflicts by a CAS .
> 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
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20138.v1.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)
