[
https://issues.apache.org/jira/browse/FLINK-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186460#comment-17186460
]
Yang Wang commented on FLINK-15946:
-----------------------------------
I believe it is not a common problem. I use our provided official yamls to
create/delete a session cluster on K8s for multiple times, it always works
well. The termination of both JobManager and TaskManager pods is fast.
The probable reason why termination gets stuck is some K8s internal
cleanup(e.g. persistent/ephemeral storage).
> Task manager Kubernetes pods take long time to terminate
> --------------------------------------------------------
>
> Key: FLINK-15946
> URL: https://issues.apache.org/jira/browse/FLINK-15946
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes, Runtime / Coordination
> Reporter: Andrey Zagrebin
> Priority: Major
>
> The problem is initially described in this [ML
> thread|https://mail-archives.apache.org/mod_mbox/flink-user/202002.mbox/browser].
> We should investigate whether and if yes, why the TM pod killing/shutdown is
> delayed by reconnecting to the terminated JM.
> cc [~fly_in_gis]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
