16601746291 opened a new issue, #19487: URL: https://github.com/apache/doris/issues/19487
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Description When we use 'BE OOM analysis' to locate a Load#Id or Query#Id that causes OOM, how do we get the SQL detail or Load context detail for this QueryId and make the error repeat? (If the doris is not pre-enabled with SET enable_profile=true) Because doris is used for application query, we often see OOM in the log, but we cannot reproduce the same sceneļ¼Also provide 'BE OOM analysis' , but it is only find which queryID cause ### Solution _No response_ ### 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]
