When a batch job finishes and the cluster is shut down the operator cannot observe the status. It is impossible to tell whether it finished or not.
Try upgrading to Flink 1.15, there this is solved. Cheers, Gyula On Tue, Oct 25, 2022 at 9:23 AM Liting Liu (litiliu) <liti...@cisco.com> wrote: > Hi, I'm deploying a flink batch job with flink-k8s-operator. > My flink-k8s-operator's version is 1.2.0 and flink's version is 1.14.6. I > found after the batch job execute finish, the jobManagerDeploymentStatus > field became "MISSING" in FlinkDeployment crd. And the error field became > "Missing JobManager deployment". > Is it better to add more information(or field) to indicate this batch job > has finished normally? > > ````` > status: > clusterInfo: > flink-revision: a921a4d @ 2022-09-09T10:18:38+02:00 > flink-version: 1.14.6 > error: Missing JobManager deployment > jobManagerDeploymentStatus: MISSING > jobStatus: > jobId: 3c5807b038300f46154d72c58f074715 > jobName: batch-job-lab-o8yln9 > savepointInfo: > lastPeriodicSavepointTimestamp: 0 > savepointHistory: [] > triggerId: '' > triggerTimestamp: 0 > triggerType: UNKNOWN > startTime: '1666681370751' > state: RECONCILING > updateTime: '1666681379021' > ```` >
