Hi Amit, upgrading Flink versions means that you should stop your jobs with a savepoint first. A new cluster with the new Flink version can be deployed next. Then, this cluster can be used to start the jobs from the previously created savepoints. Each job should pick up the work from where it stopped. See [1] for further details on how to upgrade Flink. I'm not sure about any Helm-specifics here. But I'm gonna pull Austin into the thread. He might have more insights to share.
Best, Matthias [1] https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/upgrading/#upgrading-the-flink-framework-version On Thu, Aug 26, 2021 at 9:10 AM Amit Bhatia <bhatia.amit1...@gmail.com> wrote: > Hi, > > We are using Flink 1.13.2 with Kubernetes HA solution provided by flink. > We have created a deployment for JobManager and TaskManager with option to > deploy multiple replicas and the same is bundled in a single helm chart. > So we have below queries regarding Flink upgrade strategies, kindly help > us to answer below queries: > > 1) What upgrade strategies are supported by Flink (RollingUpdate/Recreate) > and which one is recommended for production use? > > 2) During Flink upgrade from version A to version B, if we are using > rollingUpdate then at some point of time multiple versions of Flink JMs & > TMs might be running so does that can cause any corruption/failure for > running Jobs ? > > 3) During Flink upgrade from version A to version B, If we use recreate > then at some point of time if all JMs gets updated to a new version and TMs > are still updating which means TMs are running with different versions then > will this cause any corruption/failure for running Jobs? > > Regards, > Amit Bhatia >
