yuqi1129 commented on PR #8252: URL: https://github.com/apache/gravitino/pull/8252#issuecomment-3226505245
> My biggest concern is the maintainability of the clear resource logic. It seems that we are doing some complex work that should belong to the JVM level's GC, and this workload will get out of control as the project develops. > > I don't know if we have other alternative solutions to solve the OOM problem, but the current solution seems not to be the optimal one in the long run. WDYT? @jerryshao @FANNG1 I admit that the current solution is an elegant one and hard to extend, but there is no better one available for me to fix the problem. If you have any good idea, feel free to tell me. The biggest problem is that Gravitino provides a pluggable way to support multiple features, such as fileset, we can't guarantee that if there are similar problems in the jars provided by users, another points we can also introduce new jars as the project develops. No one can guarantee that the same problem will be triggered again. -- 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]
