[
https://issues.apache.org/jira/browse/HBASE-28248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-28248:
------------------------------
Priority: Critical (was: Major)
> Race between RegionRemoteProcedureBase and rollback operation could lead to
> ROLLEDBACK state be persisent to procedure store
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-28248
> URL: https://issues.apache.org/jira/browse/HBASE-28248
> Project: HBase
> Issue Type: Bug
> Components: proc-v2, Region Assignment
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.7
>
>
> And then cause load procedures failure.
> This is because we do not execute RegionRemoteProcedureBase.persistAndWake
> method in PEWorker, so even if we hold the procedureExecutionLock in
> rollback, they could be executed concurrently.
> So it is possible that in rollback, we set the state to ROLLEDBACK and delete
> the procedure, and then in persistAndWake, we persist the ROLLEDBACK state to
> procedure store.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
