Skip to content

Fix procedure lock wait scheduling#17907

Open
Caideyipi wants to merge 1 commit into
apache:masterfrom
Caideyipi:fix-procedure-lock-wait
Open

Fix procedure lock wait scheduling#17907
Caideyipi wants to merge 1 commit into
apache:masterfrom
Caideyipi:fix-procedure-lock-wait

Conversation

@Caideyipi

@Caideyipi Caideyipi commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

This PR fixes flaky procedure lock wait scheduling by moving LOCK_EVENT_WAIT enqueueing into a procedure hook instead of hard-casting ProcedureExecutor to ConfigNodeProcedureEnv. It also updates the test scheduler to enqueue waiting procedures only after the current execution attempt completes, preserves the exact procedure that should wait/yield during rollback stack handling, and makes root-stack/worker execution cleanup exception-safe. Tests: mvn -pl iotdb-core/confignode -am -Dtest=TestLockRegime#testAcquireLock -DfailIfNoTests=false -Dsurefire.failIfNoSpecifiedTests=false test; mvn -pl iotdb-core/confignode -am -Dtest=TestLockRegime#testAcquireLock,STMProcedureTest#testRolledBackProcedure -DfailIfNoTests=false -Dsurefire.failIfNoSpecifiedTests=false test

@Caideyipi Caideyipi force-pushed the fix-procedure-lock-wait branch from 984eef3 to 5b637e2 Compare June 11, 2026 03:57
@Caideyipi Caideyipi force-pushed the fix-procedure-lock-wait branch from 5b637e2 to c25849a Compare June 11, 2026 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant