morningman opened a new issue #6442: URL: https://github.com/apache/incubator-doris/issues/6442
**Is your feature request related to a problem? Please describe.** At present, some users are executing complex queries, and the CPU or IO may be full, which affects the execution of other queries. Users may not pay attention to the latency of these queries, but pay more attention to whether they can be successfully executed without affecting the normal use of the cluster. So we need to provide a mechanism to limit the resource overhead of a single query. Doris currently only supports limiting the memory overhead of a single query, but does not support limiting the CPU and IO. **Describe the solution you'd like** Achieving CPU and IO limits is a complicated matter, but we can use a simple way to achieve it according to the characteristics of Doris' query execution plan. Doris's execution plan is a volcano model. And use the push method to get data from top to bottom, and the bottom olap scan node is usually the final node. If we can limit the resource usage of the scan node, it will indirectly limit the resource overhead of the entire query (because the data is not reached, the upper node will not work) The scan node runs the scan task through a thread pool, and the scan task of a query will be split into several execution fragments for execution. Here we limit the number of scanning threads that can be used by a query to slow down the data scanning speed, thereby limiting the overall resource overhead. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
