Just to add. You can also change parallelism from checkpoints (it's usually
much faster than using savepoints). For that, you want to use external
checkpoints that are retained after job completion.
But savepoints are the way to go for any topology changes, version updates,
etc.
On Wed, Apr 21, 2
Hi Arvid,
Thanks for taking time to answer this. Yeah, we are also using save points
as only restore mechanism If job parallelism needs to be changed or some
job graph properties need to be updated. Otherwise during other rolling
deployments of task manager pods or job manager pods we solely rely
Hi Dhanesh,
We recommend to use savepoints only for migrations, investigations, A/B
testing, and time travel and rely completely on checkpoints for fault
tolerance. Are you using it differently?
Currently, we are triggering savepoints using REST apis. And query the
> status of savepoint by the re
