[FLINK-6236] [docs] Mention that resume from savepoint is possible via the web UI
This closes #3657 Project: http://git-wip-us.apache.org/repos/asf/flink/repo Commit: http://git-wip-us.apache.org/repos/asf/flink/commit/d6a1551f Tree: http://git-wip-us.apache.org/repos/asf/flink/tree/d6a1551f Diff: http://git-wip-us.apache.org/repos/asf/flink/diff/d6a1551f Branch: refs/heads/master Commit: d6a1551f90edfa534a57244a3be46e54e99dfeae Parents: 918d25e Author: rami-alisawi <[email protected]> Authored: Fri Mar 31 17:11:29 2017 +0300 Committer: Stephan Ewen <[email protected]> Committed: Fri Apr 21 12:39:05 2017 +0200 ---------------------------------------------------------------------- docs/setup/savepoints.md | 2 ++ 1 file changed, 2 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/flink/blob/d6a1551f/docs/setup/savepoints.md ---------------------------------------------------------------------- diff --git a/docs/setup/savepoints.md b/docs/setup/savepoints.md index da0784d..4bdc43f 100644 --- a/docs/setup/savepoints.md +++ b/docs/setup/savepoints.md @@ -69,6 +69,8 @@ In the above example, the print sink is stateless and hence not part of the save You can use the [command line client]({{ site.baseurl }}/setup/cli.html#savepoints) to *trigger savepoints*, *cancel a job with a savepoint*, *resume from savepoints*, and *dispose savepoints*. +With Flink >= 1.2.0 it is also possible to *resume from savepoints* using the webui. + ### Triggering Savepoints When triggering a savepoint, a single savepoint file will be created that contains the checkpoint *meta data*. The actual checkpoint state will be kept around in the configured checkpoint directory. For example with a `FsStateBackend` or `RocksDBStateBackend`:
