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

Posted to issues@flink.apache.org by "Alan Zhang (Jira)" <ji...@apache.org> on 2025/03/26 22:04:00 UTC

[jira] [Updated] (FLINK-37567) Flink clusters not be clean up when using job cancellation as suspend mechanism

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

Alan Zhang updated FLINK-37567:
-------------------------------
          Component/s: Kubernetes Operator
    Affects Version/s: kubernetes-operator-1.11.0
                       kubernetes-operator-1.10.0

> Flink clusters not be clean up when using job cancellation as suspend mechanism
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-37567
>                 URL: https://issues.apache.org/jira/browse/FLINK-37567
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.10.0, kubernetes-operator-1.11.0
>            Reporter: Alan Zhang
>            Priority: Major
>
> In general, for application mode, the Flink cluster lifecycle should be tight with the Flink job lifecycle, which means we should delete the Flink cluster if the job stopped.
> However, I noticed that Flink clusters are not deleted when I tried to suspend FlinkDeployment with "job-cancel" enabled. The CR shows the job under "CANCELED" state, but the underlying Flink cluster is still running.



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