2) What about the following: You trigger a savepoint and deploy the
2nd version from the savepoint. You let both job versions run at the
same time and switch the consumers of the job to the new version (e.g.
Kafka output topic v2). On the Flink side, this should be possible,
but moves the problem t
Hi,
hot update of a running cluster is not possible right now. And there is
also no one working on this for the near future. We are aware that this
would be nice to have, though.
For 2), this is possible, but not without stopping the job. Savepoints is
the feature that was introduced for that:
htt
Hi,
I have two questions around Flink deployment. I have done some research but
I wanted to confirm my conclusions.
1) Is it possible to do a live upgrade of a Flink cluster from one version
to the next without having to take down the entire cluster? (Imagining a
rolling deploy where we only take
