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

Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/09/05 15:12:00 UTC

[jira] [Commented] (FLINK-29200) Provide the way to delay the pod deletion for debugging purpose

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

Aitozi commented on FLINK-29200:
--------------------------------

cc [~wangyang0918] do you think it's worth to support it ? 

> Provide the way to delay the pod deletion for debugging purpose
> ---------------------------------------------------------------
>
>                 Key: FLINK-29200
>                 URL: https://issues.apache.org/jira/browse/FLINK-29200
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>            Reporter: Aitozi
>            Priority: Major
>
> Currently, if the TaskManager heartbeat timeout the pod will be deleted immediately. It's not very convenient for debugging the internal reason, eg: we can not easily get the core dump files if it's crashed for JVM bugs and so on.
> So, I purpose to introduce an option to control the delay of the pod deletion, it can be enabled to keep the pod alive for some debugging reason.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)