summaryzb opened a new issue, #2411: URL: https://github.com/apache/uniffle/issues/2411
### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) ### Search before asking - [x] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues. ### Describe the bug When spark executor memory is not enough, `WriteBufferManager#spill` will release some memory. However all the successfully sent blocks have already invoke the build-in call back `completionCallback` which releaseBlockResource related to the block release. As a result, we release the memory twice ### Affects Version(s) 0.8/0.9 ### Uniffle Server Log Output ```logtalk ``` ### Uniffle Engine Log Output ```logtalk ``` ### Uniffle Server Configurations ```yaml ``` ### Uniffle Engine Configurations ```yaml rss.client.memory.spill.enabled=true ``` ### Additional context _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! -- 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]
