You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2022/02/08 08:17:00 UTC

[jira] [Assigned] (FLINK-25968) Possible class leaks in flink-table / sql modules

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

Till Rohrmann reassigned FLINK-25968:
-------------------------------------

    Assignee: Timo Walther

> Possible class leaks in flink-table / sql modules
> -------------------------------------------------
>
>                 Key: FLINK-25968
>                 URL: https://issues.apache.org/jira/browse/FLINK-25968
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner, Table SQL / Runtime
>    Affects Versions: 1.15.0
>            Reporter: Yun Gao
>            Assignee: Timo Walther
>            Priority: Blocker
>             Fix For: 1.15.0
>
>
> This is the umbrella issues for possible class leaks in flink-table / sql planner and runtimes.
> Currently for a flink cluster, the flink classes are loaded by the system ClassLoader while each job would have separate user ClassLoaders. In this case, if some class loaded by the system ClassLoader has static variables that reference the classes loaded by the user  ClassLoaders, the user ClassLoaders would not be able to be released, which might cause class leak in some way. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)