[
https://issues.apache.org/jira/browse/FLINK-37567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Zhang updated FLINK-37567:
-------------------------------
Description:
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
Note: We used *standalone* mode to deploy Flink jobs
was:
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.
> 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
> Note: We used *standalone* mode to deploy Flink jobs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
