-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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 ThreadPool in PipelineExecutor #48146
Conversation
521e340
to
9760cdf
Compare
9760cdf
to
849403d
Compare
|
@KochetovNicolai or @vdimir can you please take a look? |
If this change is only to add metrics for pipeline executor threads, maybe we'd better add |
…tor.h) Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
1783103
to
8037aed
Compare
The motivation was to avoid using threads directly, but via ThreadPool, this:
But maybe the PipelineExecutor is special and I'm missing something and ThreadPool cannot be used there? |
I also think we should use only ThreadPool and not threads directly, ideally remove that ugly opentelemety_trace propagation difference |
Looks like there is still a problem
|
PipelineExecutor is one of the heavy user of the threads, by using pool there number of used threads for query execution can be tracked in system.metrics. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
8037aed
to
37d430d
Compare
Upgrade check failed, but it looks unrelated
|
PipelineExecutor is one of the heavy user of the threads, by using pool
there number of used threads for query execution can be tracked in
system.metrics.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Use ThreadPool in PipelineExecutor
Cc: @KochetovNicolai @vdimir