I attended Jamie Grier’s excellent presentation at Flink Forward today ("Robust
Stream Processing with Apache Flink” -
http://flink-forward.org/kb_sessions/robust-stream-processing-with-apache-flink/
<http://flink-forward.org/kb_sessions/robust-stream-processing-with-apache-flink/>)
where he showed recovery from a savepoint. It took at least 3 steps - create
the savepoint, kill the current job, start from savepoint. Is it possible to
combine these into a single action - not just from the tooling perspective
(where I think it’s pretty straightforward to simulate what I’m asking for
here) but to actually have the running job STOP once it processes the save
point request AND start a new job from that savepoint?
What I’m looking to reduce the gap between the savepoint creation AND the
stopping of the current task as well as reducing the gap between stopping the
current job and starting a new job from the savepoint.
Ron
—
Ron Crocker
Principal Engineer & Architect
( ( •)) New Relic
rcroc...@newrelic.com
M: +1 630 363 8835
