wiedld opened a new issue, #11523: URL: https://github.com/apache/datafusion/issues/11523
### Is your feature request related to a problem or challenge? When asking for more memory via the [memory reservation](https://github.com/apache/datafusion/blob/b0925c801e1c07bd78c78b045ab58fbd0630b638/datafusion/execution/src/memory_pool/mod.rs#L186), the [error returned from the underlying memory pool](https://github.com/apache/datafusion/blob/b0925c801e1c07bd78c78b045ab58fbd0630b638/datafusion/execution/src/memory_pool/pool.rs#L235-L240) focuses on that specific request. As a result, when debugging a resource exhausted error, we get an error message that looks something like: ``` Failed to allocate additional 795696944 bytes for RepartitionExec[1] with 3182787776 bytes already allocated - maximum available is 63296515 ``` This^^ error is about what next incremental request failed to get more memory, and **not about what is using the most memory**. As a result, additional dev time has to be spent to (a) at best, track down the actual high memory consumer and (b) at worst, wasted time chasing the wrong memory consumer. ### Describe the solution you'd like One possible solution is to have the error message returned the Top K memory consumers. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- 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]
