Hi Alan! I think it should be possible to address this gap for most cases. We don't have the same robust way of getting the last-state information for session jobs as we do for applications, so it will be slightly less reliable overall. For session jobs the last checkpoint info has to be queried from the JM rest api, so as long that is available it should work fine.
I am not aware of anyone working on this at the moment, it would be great if you could open a JIRA ticket to track this. If you are interested in working on this, we can also support you but this is a fairly complex feature that involves many layers of operator logic. Cheers, Gyula On Tue, Apr 30, 2024 at 1:08 AM Alan Zhang <shuai....@gmail.com> wrote: > Hi, > > We wanted to use the Apache Flink Kubernetes operator to manage the > lifecycle of our Flink jobs in Flink session clusters. And we wanted to > have the "last-state" upgrade feature for our use cases. > > However, the latest official doc states the "last-state" upgrade mode is > not supported in the session mode(aka. FlinkSessionJob) currently: > https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/custom-resource/job-management/#stateful-and-stateless-application-upgrades > > Last state upgrade mode is currently only supported for FlinkDeployments. > > Why didn't we support this upgrade mode in session mode? Do we have a plan > to address this gap? Any suggestions for us if we want to stick with > session mode? > > -- > Thanks, > Alan >
