wu-a-ge commented on issue #4915: URL: https://github.com/apache/seatunnel/issues/4915#issuecomment-1614872481
> > > @chaorongzhi may be zeta engize's bug,I found it's history service never delete finished jobs!!! > > > > > > You're right. You've been running a lot of jobs? > > Can this be solved by caching the SeaTunnelChildFirstClassLoader instead of re-creating the SeaTunnelChildFirstClassLoader instance each time？  have removed SeaTunnelChildFirstClassLoader this class, put all the plug-ins in the lib directory, metaspace did rise slowly, at the same time, I have already solved the problem JobHistoryService cache data time is too long, But it still feels like metaspace memory inflation is not being solved. I am somewhat reverting to the zeta engine using hazelcast's serialization and disordering. It could be that the zeta engine is not working properly, or it could be hazelcast itself -- 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]
