[
https://issues.apache.org/jira/browse/FLINK-18702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165385#comment-17165385
]
Yangze Guo commented on FLINK-18702:
------------------------------------
I think it is indeed the same issue as FLINK-11205. Not sure does it make sense
to backport Flink-16408. As a workaround, you could increase the
taskmanager.memory.jvm-metaspace.size[1].
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.11/ops/config.html#taskmanager-memory-jvm-metaspace-size
> Flink elasticsearch connector leaks threads and classloaders thereof
> --------------------------------------------------------------------
>
> Key: FLINK-18702
> URL: https://issues.apache.org/jira/browse/FLINK-18702
> Project: Flink
> Issue Type: Bug
> Components: Connectors / ElasticSearch
> Affects Versions: 1.10.0, 1.10.1
> Reporter: Jun Qin
> Assignee: Jun Qin
> Priority: Major
>
> Flink elasticsearch connector leaking threads and classloaders thereof. This
> results in OOM Metaspace when ES sink fails and restarted many times.
> This issue is visible in Flink 1.10 but not in 1.11 because Flink 1.11 does
> not create new class loaders in case of recoveries (FLINK-16408)
>
> Reproduction:
> * Start a job with ES sink in a Flink 1.10 cluster, without starting the ES
> cluster.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
