[
https://issues.apache.org/jira/browse/BEAM-6460?focusedWorklogId=187141&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-187141
]
ASF GitHub Bot logged work on BEAM-6460:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jan/19 23:16
Start Date: 18/Jan/19 23:16
Worklog Time Spent: 10m
Work Description: mxm commented on issue #7552: [BEAM-6460] Remove cached
class references upon start/shutdown
URL: https://github.com/apache/beam/pull/7552#issuecomment-455718167
I have yet to verify this with @djhworld, but from my analysis the reported
problem comes either from an incorrect packaging of the jar or from the use of
Flink's `parent-first` classloader. Both lead to using Flink's internal version
of Jackson, instead of the user-provided one. This can let the classloader leak.
That said, the fix in this PR has been verified to fix the @djhworld's
problem, so I'm leaning towards merging it.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 187141)
Time Spent: 1h 40m (was: 1.5h)
> PipelineOptionsFactory 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: 1h 40m
> 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)
