[
https://issues.apache.org/jira/browse/FLINK-33623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790585#comment-17790585
]
Matthias Pohl commented on FLINK-33623:
---------------------------------------
Thanks for raising this issue, [~gabry.wu]. Can you provide a minimal Flink
example that makes this reproducible? It's hard to identify where the
classloader is coming from (I couldn't find any code segment where the
classloading is explicitly set). I'm wondering whether it's related to
FLINK-25023. In FLINK-25023 we experience a classloader leak which is caused by
the fact that certain user code might trigger the thread creation (in the case
of FLINK-33623: the thread that's used by the netty client) where the thread
derives the classloader from the user code (see the [FLINK-25023 PR
comment|https://github.com/apache/flink/pull/17916#discussion_r761288714] from
[~dmvk] for a more detailed description of what's going on)
What do you mean by the following text snippet in the issue description:
{quote}TIPs
classloader.check-leaked-classloader = false
{quote}
> Metaspce leak caused by Flink Netty Client thread
> -------------------------------------------------
>
> Key: FLINK-33623
> URL: https://issues.apache.org/jira/browse/FLINK-33623
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.13.5, 1.18.0
> Reporter: gabrywu
> Priority: Minor
> Attachments: image-2023-11-23-09-47-50-536.png
>
>
> Hi, folks,
> We found that there is a Flink Netty Client thread with contextClassLoader
> `ChildFirstClassLoader`, and it causes a metaspace leak.
> TIPs
> classloader.check-leaked-classloader = false
>
> !image-2023-11-23-09-47-50-536.png|width=1175,height=651!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
