[ https://issues.apache.org/jira/browse/FLINK-10352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann updated FLINK-10352: ---------------------------------- Fix Version/s: (was: 1.7.0) > Bind Task's URLClassLoader to TaskExecutor's slot > ------------------------------------------------- > > Key: FLINK-10352 > URL: https://issues.apache.org/jira/browse/FLINK-10352 > Project: Flink > Issue Type: Improvement > Components: Distributed Coordination > Affects Versions: 1.5.3, 1.6.0, 1.7.0 > Reporter: Till Rohrmann > Assignee: Jiayi Liao > Priority: Major > Fix For: 1.8.0 > > > The {{Task's}} {{URLClassLoader}} is used to dynamically load user code > classes. The lifetime of this class loader is bound to the {{Task}} and, > thus, it can happen that we generate multiple class loader for the same job > if multiple {{Tasks}} are deployed to the same slot successively. > We could avoid this situation by binding the lifetime of the > {{URLClassLoader}} to the slot instead of the {{Task}}. The slot will only be > released if the {{JobMaster}} no longer needs it. That way we won't > potentially recreate the {{URLClassLoader}} for every submitted {{Task}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)