[
https://issues.apache.org/jira/browse/FLINK-38375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047215#comment-18047215
]
xiaolong3817 commented on FLINK-38375:
--------------------------------------
hi
Has anyone paid attention to this issue?
> Flink Resouce leak on Flink k8s
> -------------------------------
>
> Key: FLINK-38375
> URL: https://issues.apache.org/jira/browse/FLINK-38375
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.20.2
> Reporter: xiaolong3817
> Priority: Critical
> Labels: pull-request-available
> Attachments: jm_failover_log.png
>
>
> Hello, when using Flink on Kubernetes (K8s), we encountered an issue where
> *TaskManager resources failed to be released* following an abnormal shutdown
> of the JobManager. The abnormal JM shutdown scenarios include Out-of-Memory
> (OOM) errors, forced termination via the {{kill -9}} command, or physical
> machine failures.
> Currently, our Flink cluster operates in *Application Mode* on K8s. This
> resource leakage issue (failure to release TM resources) can be *100%
> reproduced* whenever the JM shuts down abnormally.
> * Flink version in use: *1.20.2*
> Our current relevant configurations are as follows:
> * {{jobmanager.scheduler: Adaptive}}
> * {{resourcemanager.previous-worker.recovery.timeout: 0}}
> This is my analysis document：
> [https://docs.google.com/document/d/1-8Iz-oOkW5YozebjqVOvmmHvVVLVnUA7qcu8GVeNnv4/edit?usp=sharing]
>
> the numSlots by report is 2, But I configured it as 1
> !jm_failover_log.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
