fix: change RLock to Lock in sync manager methods #15546
Merged
+6
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #15218
Motivation
The
CheckWorkflowExistence,Release, andReleaseAllmethods in the sync manager were using read locks (RLock) when they should be using write locks (Lock). These methods modify the internal state of the sync manager (accessing and potentially modifyingsm.syncLockMap), which requires exclusive write access rather than shared read access.Modifications
Changed the following methods from using
RLock()/RUnlock()toLock()/Unlock():CheckWorkflowExistence()- iterates and modifies sync lock mapRelease()- modifies sync lock map entriesReleaseAll()- modifies sync lock map entriesThis ensures proper synchronization and prevents race conditions when multiple goroutines access these methods concurrently.
Verification
Documentation
No documentation changes needed - this is an internal synchronization fix.
AI
Co-authored with Claude