[
https://issues.apache.org/jira/browse/FLINK-36876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904764#comment-17904764
]
Gyula Fora commented on FLINK-36876:
------------------------------------
I originally thought that the fix would involve simply passing an executor
service but seems like it needs a core Flink change. Is there any operator only
fix maybe?
> Operator Heap Memory Leak
> -------------------------
>
> Key: FLINK-36876
> URL: https://issues.apache.org/jira/browse/FLINK-36876
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.6.1, kubernetes-operator-1.10.0
> Environment:
> Flink Operator Version: 1.6.1 (I think the latest version 1.10 has the same
> problem)
>
> JDK: openjdk version "11.0.24"
>
> GC: G1
>
> FlinkDeployment ammout: 3000+
>
> Reporter: chenyuzhi
> Assignee: chenyuzhi
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2024-12-10-15-57-00-309.png,
> image-2024-12-10-16-09-22-749.png, image-2024-12-10-16-11-21-830.png,
> screenshot-1.png
>
>
> When the amount of FlinkDeployment increasing, the heap memory used by
> Kubernetes Operator keep increasing.
> Eventhough after Old GC, the heap memory used can not be decreased as
> expected.
> !image-2024-12-10-15-57-00-309.png|width=443,height=541!
> Finally, the Kubernetes Operator was OOMKilled by OS;
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
