Prevent Virtual Thread Deadlocks by Replacing Synchronized Blocks #381
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.
This PR replaces synchronized blocks in the YDB SDK with ReentrantLock implementations to resolve deadlocks that occur when using AsyncReader with Java 23 virtual threads. Synchronized blocks inadvertently pin virtual threads to carrier threads, leading to thread starvation in high-concurrency scenarios.
This change unblocks adoption of virtual threads in YDB applications while maintaining backward compatibility.
Example stacktrace of the pinned virtual thread