[ https://issues.apache.org/jira/browse/HBASE-28248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-28248: ------------------------------ Component/s: proc-v2 Region Assignment > 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 > Priority: Major > > 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)