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

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/10/25 05:00:00 UTC

[jira] [Assigned] (FLINK-29609) Clean up jobmanager deployment on suspend after recording savepoint info

     [ https://issues.apache.org/jira/browse/FLINK-29609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora reassigned FLINK-29609:
----------------------------------

    Assignee: Sriram Ganesh

> Clean up jobmanager deployment on suspend after recording savepoint info
> ------------------------------------------------------------------------
>
>                 Key: FLINK-29609
>                 URL: https://issues.apache.org/jira/browse/FLINK-29609
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Sriram Ganesh
>            Priority: Major
>             Fix For: kubernetes-operator-1.3.0
>
>
> Currently in case of suspending with savepoint. The jobmanager pod will linger there forever after cancelling the job.
> This is currently used to ensure consistency in case the operator/cancel-with-savepoint operation fails.
> Once we are sure however that the savepoint has been recorded and the job is shut down, we should clean up all the resources. Optionally we can make this configurable.



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