You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/22 00:04:00 UTC

[jira] [Work logged] (BEAM-6460) Jackson Cache may hold on to Classloader after pipeline restart

     [ https://issues.apache.org/jira/browse/BEAM-6460?focusedWorklogId=187931&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-187931 ]

ASF GitHub Bot logged work on BEAM-6460:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Jan/19 00:03
            Start Date: 22/Jan/19 00:03
    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-456228594
 
 
   Run Flink ValidatesRunner
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 187931)
    Time Spent: 1h 50m  (was: 1h 40m)

> 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: 1h 50m
>  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)