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.

Sign up for GitHub

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

Jump to bottom

branch-3.0: [bugfix](be) split the usage of thread pool in internal service #49292 #49324

Open
wants to merge 1 commit into
base: branch-3.0
Choose a base branch
from
Open

branch-3.0: [bugfix](be) split the usage of thread pool in internal service #49292 #49324

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link
Contributor

Cherry-picked from #49292

@yiguolei
[bugfix](be) split the usage of thread pool in internal service (#49292)
a420d4d 
### What problem does this PR solve?

There are many wrong usage of light,heavy,arrow thread pool in internal
service. And they will affect each other. I spilt them and distinguish
the usage of them:
1. light threadpool should be only used in query processing logic. All
hanlers should be very light, not locked.
2. heavy threadpool is used for load process and other process that will
read disk or access network.
@github-actions github-actions bot requested a review from dataroaring as a code owner March 20, 2025 11:00
@Thearas
Copy link
Contributor

Thearas commented Mar 20, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Mar 20, 2025
@Thearas
Copy link
Contributor

Thearas commented Mar 20, 2025

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dataroaring dataroaring Awaiting requested review from dataroaring dataroaring is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@Thearas @dataroaring @yiguolei