Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use double checked locking in OperatorAdaptor #21297

Merged
merged 2 commits into from
Mar 28, 2024

Conversation

sopel39
Copy link
Member

@sopel39 sopel39 commented Mar 27, 2024

Description

Synchronizing on get() method causes planning
congestion when there is high query concurrency.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@sopel39 sopel39 added the no-release-notes This pull request does not require release notes entry label Mar 27, 2024
@sopel39 sopel39 requested review from dain and raunaqmorarka March 27, 2024 21:17
@cla-bot cla-bot bot added the cla-signed label Mar 27, 2024
sopel39 added 2 commits March 28, 2024 11:28
Synchronizing on get() method causes planning
congestion when there is high query concurrency.
@sopel39 sopel39 changed the title Remove synchronization in OperatorAdaptor Use double checked locking in OperatorAdaptor Mar 28, 2024
@sopel39 sopel39 merged commit 9ec2b07 into trinodb:master Mar 28, 2024
94 of 95 checks passed
@sopel39 sopel39 deleted the ks/remove_lock branch March 28, 2024 13:11
@github-actions github-actions bot added this to the 444 milestone Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed no-release-notes This pull request does not require release notes entry
Development

Successfully merging this pull request may close these issues.

3 participants