DanielLeens commented on issue #12456: URL: https://github.com/apache/seatunnel/issues/12456#issuecomment-5917739187
Classification: A / Zeta resource management and class-loader lifecycle. The live-heap paths now provide the missing retaining-edge evidence for the reported 2.3.13 deployment. They identify two different post-release roots: Hadoop's static `WritableComparator.comparators` retains a `Configuration` whose `classLoader` is the released child loader, while MongoDB's live `BufferPoolPruner` thread retains the other child loader through both its thread factory class and inherited access-control context. This is strong evidence of retention after `releaseClassLoader`, but it does not establish that both roots are present on current `dev`, nor that the opt-in close work in #10678 removes either root. Please do not apply a broad class-loader cleanup or clear a process-wide Hadoop cache based on this one deployment. The next safe step is two minimal current-`dev` reproducers, one for each root. For each, record the exact connector/JAR set, the loader count and Metaspace before and after a forced GC, the complete textual root path, and the result after one identical second job. A proposed fix must show that it removes only the job-owned reference without breaking another concurrent job that shares Hadoop or MongoDB process state. That evidence will determine whether the fixes should be independent and whether #10678 is relevant to either one. -- 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]
