[ 
https://issues.apache.org/jira/browse/HBASE-27223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated HBASE-27223:
-----------------------------
    Assignee: chenglei
      Status: Patch Available  (was: Open)

> Avoid data inconsistent between primary and secondary replicas for the new 
> region replication framework
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-27223
>                 URL: https://issues.apache.org/jira/browse/HBASE-27223
>             Project: HBase
>          Issue Type: Bug
>          Components: read replicas
>    Affects Versions: 3.0.0-alpha-3
>            Reporter: chenglei
>            Assignee: chenglei
>            Priority: Major
>
> For the new region replication framework introduced by HBASE-26233, when we 
> write the {{Mutation}} on primary region replica , if 
> {{HRegion.doMiniBatchMutate}}  throws a exception, for example ,{{WAL.sync}} 
> throws a {{TimeoutIOException}} because sync timeout, the writing on primary 
> region replica is failed and we could not query the {{Mutation}} on the 
> primary region replica because of {{Mutation}} is not written to the 
> {{MemStore}}, but the replication to the second replica may be successful 
> because we always execute 
> {{MultiVersionConcurrencyControl.WriteEntry.runCompletionAction}} in 
> {{MultiVersionConcurrencyControl.complete}} , and we could get the 
> {{Mutation}} on the secondary region replica, this inconsistency should be  
> avoid even if it is short. 
> But for {{WALUtil.writeMarker}}, we should always replicate to the second 
> replica even though {{WAL.sync}} is failed, because we just want to sync 
> region state to secondary replica.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to