You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the workload setting for merges and mutations.
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.
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: