Details
-
Bug
-
Status: Resolved
-
P0
-
Resolution: Workaround
-
2.7.0
-
None
Description
It looks like Jackson has an internal cache which may continue to hold the Flink application classloader through its TypeFactory class. When the pipeline is restarted due to a failure, a new classloader is created which can result in too many classes being loaded.
Reported on the user mailing list: https://lists.apache.org/thread.html/e201891684ef3dcffce48d20d1f9be0e19fc2294334362cc7092c0ff@%3Cuser.beam.apache.org%3E
Attachments
Issue Links
- is cloned by
-
BEAM-6996 LTS Backport: Jackson Cache may hold on to Classloader after pipeline restart
- Resolved
- is related to
-
FLINK-10928 Job unable to stabilise after restart
- Closed
- links to