-
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
Workload classification for merges and mutations #63211
Labels
Comments
Also, we should pay attention to the existing scheduler of a background thread pool. We should avoid running tasks that are blocked by the IO scheduler, but occupy a thread in the background pool, blocking other tasks. It could lead to "priority inversion" of a kind. |
31 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a setting
workload
that allows to specify how a query should be classified for resource consumption (only IO resources at the moment). We need a way to specify theworkload
setting for merges and mutations.Use case
workload
for different tables provides a way to prioritize merges of specific tables.workload
for merges and mutations provides a way to prioritize one over another.Describe the solution you'd like
Add a server and a merge tree settings
merge_workload
andmutation_workload
.The text was updated successfully, but these errors were encountered: