How does StreamPark recover a Flink job from a savepoint after a Console restart?

StreamPark Console being restarted (a deploy, an upgrade, a host reboot) shouldn't take down the Flink jobs it manages, and the design reflects that: Console is a control-plane process, not the thing keeping jobs alive.

Already-running jobs on YARN or Kubernetes keep running independently of Console's own process lifecycle, because they were submitted as their own cluster applications/pods, not as child processes of Console. When Console comes back up, it reconnects to each job using the Application/Job ID it had persisted to its metadata database before the restart, and resumes polling status from there — no savepoint or restart of the Flink job itself is needed purely because Console restarted.

A savepoint-based recovery only becomes relevant if the underlying Flink job itself was also lost or intentionally stopped — for example the YARN Application actually died, not just Console. In that case, starting the Application again in StreamPark uses the last savepoint path recorded against it, so the new job instance resumes state from that savepoint rather than reprocessing history, closing the gap between "the job stopped" and "the job is back to where it left off."