You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2019/04/03 16:50:02 UTC
[jira] [Commented] (BEAM-6460) Jackson Cache may hold on to
Classloader after pipeline restart
[ https://issues.apache.org/jira/browse/BEAM-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808917#comment-16808917 ]
Kenneth Knowles commented on BEAM-6460:
---------------------------------------
I am making the Fix Version a single value, which would indicate which release notes this is linked to, and the first version where it is resolved. I will make a clone for the LTS backport to 2.7.1.
> Jackson Cache may hold on to Classloader after pipeline restart
> ---------------------------------------------------------------
>
> Key: BEAM-6460
> URL: https://issues.apache.org/jira/browse/BEAM-6460
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.7.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Blocker
> Fix For: 2.10.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)