[HBASE-27223] Avoid data inconsistent between primary and secondary replicas for the new region replication framework

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.0.0-alpha-3
• Component/s: read replicas
• Assignee: chenglei
• Reporter: chenglei
• Created: 19/Jul/22 09:54
• Updated: 22/Jul/22 02:42
• Resolved: 22/Jul/22 02:40

Description

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.

Issue Links

• links to: GitHub Pull Request #4633