shaotianfeng opened a new issue, #25604: URL: https://github.com/apache/doris/issues/25604
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Version doris operating environment and configuration: 6 clusters, 4 fe and be mixed, 2 be alone, doris version 2.0.1. About the limit query, limit 1, after the output result 1, the background will still perform a large number of calculations, the big table 1.7 billion data, the small table 50 million data, Run select s1.* from ele_5000_1 s1 join ele_5000 s2 where s1.ele_id=s2.ele_id limit 1.. doris运行环境和配置：6台集群，4台fe和be混用，2台单独be，doris版本2.0.1。关于limit查询，limit 1，输出结果1条后，后台仍会进行大量计算的问题，大表17亿条数据，小表5千万数据，在执行select s1.* from ele_5000_1 s1 join ele_5000 s2 where s1.ele_id=s2.ele_id limit 1 。 ### What's Wrong? When executing this statement query, the result can be produced in one or two seconds, but there will still be a lot of resources (cpu, memory, bandwidth) in the background, and these resources will be released after a period of time. 在执行这条语句查询时，一二秒可以出结果，但后台仍会存在大量资源（cpu、内存、带宽）利用，一段时间后这些资源才会释放. ### What You Expected? Can you provide a solution, or what configuration changes need to be made. 请问能否给出一个解决方案，或者说需要进行什么配置修改。 ### How to Reproduce? If there are 1.7 billion data in the big table and 50 million data in the small table, run select s1.* from ele_5000_1 s1 join ele_5000 s2 where s1.ele_id=s2.ele_id limit 1. 大表17亿条数据，小表5千万数据，在执行select s1.* from ele_5000_1 s1 join ele_5000 s2 where s1.ele_id=s2.ele_id limit 1 。 ### Anything Else? no. 没有了 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
