[
https://issues.apache.org/jira/browse/FLINK-16408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058862#comment-17058862
]
Stephan Ewen commented on FLINK-16408:
--------------------------------------
I think it should be okay to fix in a 1.10.x release, but want to double check.
It may have some implications, for example statics not being re-initialized in
restart, because the same classloader is being used.
I would assume this to be okay, in fact, really helpful in most cases, but
wanted to check if someone would see a concern with changing this behavior.
> Bind user code class loader to lifetime of a slot
> -------------------------------------------------
>
> Key: FLINK-16408
> URL: https://issues.apache.org/jira/browse/FLINK-16408
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.9.2, 1.10.0
> Reporter: Till Rohrmann
> Priority: Critical
> Fix For: 1.10.1, 1.11.0
>
>
> In order to avoid class leaks due to creating multiple user code class
> loaders and loading class multiple times in a recovery case, I would suggest
> to bind the lifetime of a user code class loader to the lifetime of a slot.
> More precisely, the user code class loader should live at most as long as the
> slot which is using it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
