You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2018/08/29 13:15:40 UTC

[GitHub] GodfreyJohnson opened a new pull request #6630: [FLINK-9043] restore from the latest job's completed checkpoint with …

GodfreyJohnson opened a new pull request #6630: [FLINK-9043] restore from the latest job's completed checkpoint with …
URL: https://github.com/apache/flink/pull/6630
 
 
     - For [FLINK-9043](https://issues.apache.org/jira/browse/FLINK-9043?filter=-6&jql=project%20%3D%20FLINK%20AND%20created%20%3E%3D%20-1w%20order%20by%20created%20DESC)
   
     ## What is the purpose of the change
   
     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. 
   
     - Each flink job has 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)
   
     ## Brief change log
   
     - add hdfs utils to get the latest job completed checkpoint metadata path
     - recover from the metadata path for legacy mode and new mode
   
     ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
     - The S3 file system connector: (no)
   
     ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not documented)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services