maobaolong opened a new issue, #1932: URL: https://github.com/apache/incubator-uniffle/issues/1932
### 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 During these day, we found a bundle of memory related issue, some are memory leak, some are double release, these make us confusing. And we have a discussion between our teammate, an idea is that we should decouple rpc thread and memory release thread by a blocking queue, leverage this queue, let's say it `releaseEventQueue`, rpc threads could be memory release event producer, and memory release thread poll the `releaseEventQueue` and release the memory, by this, we can make sure release memory within one thread, double release behavior can be detected and avoid. Any thoughts? ### Affects Version(s) master ### Uniffle Server Log Output _No response_ ### Uniffle Engine Log Output _No response_ ### Uniffle Server Configurations _No response_ ### Uniffle Engine Configurations _No response_ ### Additional context _No response_ ### Are you willing to submit PR? - [ ] 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]
