refactor(meta-service0): rotbl: use spawn_blocking() instead blocking_in_place()
#18717
+51
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
pr-refactor
drmingdrmer
force-pushed
the
stream-mget
branch
2 times, most recently
from
a750548 to
aff28fb
Compare
…ing_in_place()` `blocking_in_place()` may still exhaust the worker threads.
drmingdrmer
force-pushed
the
stream-mget
branch
from
aff28fb to
300f411
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
refactor(meta-service0): rotbl: use
spawn_blocking()insteadblocking_in_place()blocking_in_place()may still exhaust the worker threads.chore: test TimedFuture for blocking_in_place and spawn_blocking
Tests
Type of change
Related Issues
This change is