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

2019-04-03 Thread Kenneth Knowles (JIRA)


 [ 
https://issues.apache.org/jira/browse/BEAM-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kenneth Knowles updated BEAM-6460:
--
Fix Version/s: (was: 2.11.0)

> 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)


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

2019-04-03 Thread Kenneth Knowles (JIRA)


 [ 
https://issues.apache.org/jira/browse/BEAM-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kenneth Knowles updated BEAM-6460:
--
Fix Version/s: (was: 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, 2.11.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)


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

2019-01-31 Thread Maximilian Michels (JIRA)


 [ 
https://issues.apache.org/jira/browse/BEAM-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maximilian Michels updated BEAM-6460:
-
Fix Version/s: 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.7.1, 2.10.0, 2.11.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)


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

2019-01-18 Thread Maximilian Michels (JIRA)


 [ 
https://issues.apache.org/jira/browse/BEAM-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maximilian Michels updated BEAM-6460:
-
Summary: Jackson Cache may hold on to Classloader after pipeline restart  
(was: PipelineOptionsFactory may hold on to Classloader after pipeline restart)

> 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 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)