You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Andrey Zagrebin (Jira)" <ji...@apache.org> on 2020/02/07 08:00:00 UTC

[jira] [Commented] (FLINK-15946) Task manager Kubernetes pods take long time to terminate

    [ https://issues.apache.org/jira/browse/FLINK-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032180#comment-17032180 ] 

Andrey Zagrebin commented on FLINK-15946:
-----------------------------------------

[~flyd1005] 

Could you describe the problem details again here? Does it happen with the latest Flink 1.9 and/or 1.10 RC?

Could you share full TM logs and minimum source code of a job where it is reproducible?

> 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)