[
https://issues.apache.org/jira/browse/FLINK-28478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-28478.
------------------------------
Resolution: Fixed
Merged to main a6430378553d7405a037f948576bea5ef5be55ce
> Session Cluster will lost if it failed between status recorded and deploy
> -------------------------------------------------------------------------
>
> Key: FLINK-28478
> URL: https://issues.apache.org/jira/browse/FLINK-28478
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.1.0
> Reporter: Aitozi
> Assignee: Gyula Fora
> Priority: Critical
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.1.0
>
>
> When I test case with https://issues.apache.org/jira/browse/FLINK-28187
> I hit that the session cluster deploy can not be deployed if it fails between
> status recorded and deploy. Because, in the next reconcile loop, the spec is
> not detected changed by {{checkNewSpecAlreadyDeployed}}, so it will not try
> to start the session cluster again.
> The application mode have no problem, because the deployed spec SUSPEND state
> of the job is not equal to the desired state, so it will try to reconcile the
> spec change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
