yuqi1129 commented on PR #8252: URL: https://github.com/apache/gravitino/pull/8252#issuecomment-3226508985
> > 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 > > Yes, the current solution depends on the implementation logic of dependency jars. classloader reuse mentioned by @jerryshao is a more general way, but my concern is the time for 1.0 and may introduce some unexpected behavior before the release. A cache mechanism can alleviate the problem, but it cannot fix it at its source. Since we are using Caffeine cache for the catalog manager, the class loader will be recreated if the cache expires. -- 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]
