[
https://issues.apache.org/jira/browse/FLINK-27337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525579#comment-17525579
]
Aitozi commented on FLINK-27337:
--------------------------------
As discussed in the [mailing
list|https://lists.apache.org/thread/9xvdwtf5tbr28lonj21p58tn5gdndns5], the
deletion of all the session job may be a critical operation. So if there is an
upgrade or cleanup event for the session cluster, we can postpone the real
cleanup/stop until all the session job suspended by user. We can avoid to
remove the finializer and re-schedule to check whether all the job are stopped.
This way is more safe but may involve more step when user want to delete or
upgrade the session cluster, what about make it both supported.
> Prevent session cluster to be deleted when there are running jobs
> -----------------------------------------------------------------
>
> Key: FLINK-27337
> URL: https://issues.apache.org/jira/browse/FLINK-27337
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Yang Wang
> Priority: Major
> Fix For: kubernetes-operator-1.0.0
>
>
> We should prevent the session cluster to be deleted when there are running
> jobs.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
