alamb commented on issue #7858: URL: https://github.com/apache/arrow-datafusion/issues/7858#issuecomment-1777723893
I think another issue is that the RepartitionExec reserves memory on demand, so if memory is almost out (as it has been consumed by the AggregateExec) it may not be able to get even a small amount. The way to get the query to run is to restrict the memory used by the AggregateExec so there is still reasonable memory available for other operators One potential thing would be to use a different memory strategy (e.g. a `Fair` pool) -- 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]
