[
https://issues.apache.org/jira/browse/FLINK-9043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596318#comment-16596318
]
godfrey johnson edited comment on FLINK-9043 at 8/30/18 1:54 AM:
-----------------------------------------------------------------
[https://github.com/GodfreyJohnson/flink/commit/3338b4c1974c018410f438cfc6f12968c8df5fa6]
[https://github.com/apache/flink/pull/6633]
I added a patch for restoring from the latest job's completed checkpoint with
hdfs path.
What we aim to do is to recover from the hdfs path automatically with the
latest job's completed checkpoint. Currently, we can use 'run -s' with the
metadata path manully, which is easy for single flink job to recover. But we
have managed a lot of flink jobs, we want each flink job recovered just like
spark streaming with getorcreate method from the latest completed jobs, without
records lost.
For this patch,
- Each flink job should have it own hdfs checkpoint path
- Only support for HDFS(hdfs:// or viewfs://)
- Support for RocksDBStateBackend and FsStateBackend
- Support for legacy mode and new mode(dynamic scaling)
was (Author: godfrey):
[https://github.com/GodfreyJohnson/flink/commit/12b7d5332610273d1ac79ee4593c31994c69fee9]
[https://github.com/apache/flink/pull/6630]
I added a patch for restoring from the latest job's completed checkpoint with
hdfs path.
What we aim to do is to recover from the hdfs path automatically with the
latest job's completed checkpoint. Currently, we can use 'run -s' with the
metadata path manully, which is easy for single flink job to recover. But we
have managed a lot of flink jobs, we want each flink job recovered just like
spark streaming with getorcreate method from the latest completed jobs, without
records lost.
For this patch,
- Each flink job should have it own hdfs checkpoint path
- Only support for HDFS(hdfs:// or viewfs://)
- Support for RocksDBStateBackend and FsStateBackend
- Support for legacy mode and new mode(dynamic scaling)
> Introduce a friendly way to resume the job from externalized checkpoints
> automatically
> --------------------------------------------------------------------------------------
>
> Key: FLINK-9043
> URL: https://issues.apache.org/jira/browse/FLINK-9043
> Project: Flink
> Issue Type: New Feature
> Reporter: godfrey johnson
> Assignee: Sihua Zhou
> Priority: Major
> Labels: pull-request-available
>
> I know a flink job can reovery from checkpoint with restart strategy, but can
> not recovery as spark streaming jobs when job is starting.
> Every time, the submitted flink job is regarded as a new job, while , in the
> spark streaming job, which can detect the checkpoint directory first, and
> then recovery from the latest succeed one. However, Flink only can recovery
> until the job failed first, then retry with strategy.
>
> So, would flink support to recover from the checkpoint directly in a new job?
> h2. New description by [~sihuazhou]
> Currently, it's quite a bit not friendly for users to recover job from the
> externalized checkpoint, user need to find the dedicate dir for the job which
> is not a easy thing when there are too many jobs. This ticket attend to
> introduce a more friendly way to allow the user to use the externalized
> checkpoint to do recovery.
> The implementation steps are copied from the comments of [~StephanEwen]:
> - We could make this an option where you pass a flag (-r) to automatically
> look for the latest checkpoint in a given directory.
> - If more than one jobs checkpointed there before, this operation would fail.
> - We might also need a way to have jobs not create the UUID subdirectory,
> otherwise the scanning for the latest checkpoint would not easily work.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
