[ 
https://issues.apache.org/jira/browse/FLINK-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857579#comment-16857579
 ] 

Yu Li commented on FLINK-12619:
-------------------------------

Although FLINK-6755 and this one are related, they actually don't block each 
other, or say stop-with-checkpoint is a valid and valuable feature no matter 
whether we allow users to trigger checkpoint manually or not.

What's more, as mentioned in the description, stop-with-checkpoint would make 
it possible to have no source rewinding during job recovery, while triggering 
checkpoint from CLI (and then stop) cannot assure this, so FLINK-6755 cannot 
supersede this one (no matter what the decision is there). I think this is also 
the reason why FLINK-11458 is proposed/implemented while user already could 
trigger savepoint from CLI.

> Support TERMINATE/SUSPEND Job with Checkpoint
> ---------------------------------------------
>
>                 Key: FLINK-12619
>                 URL: https://issues.apache.org/jira/browse/FLINK-12619
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / State Backends
>            Reporter: Congxian Qiu(klion26)
>            Assignee: Congxian Qiu(klion26)
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Inspired by the idea of FLINK-11458, we propose to support terminate/suspend 
> a job with checkpoint. This improvement cooperates with incremental and 
> external checkpoint features, that if checkpoint is retained and this feature 
> is configured, we will trigger a checkpoint before the job stops. It could 
> accelarate job recovery a lot since:
> 1. No source rewinding required any more.
> 2. It's much faster than taking a savepoint since incremental checkpoint is 
> enabled.
> Please note that conceptually savepoints is different from checkpoint in a 
> similar way that backups are different from recovery logs in traditional 
> database systems. So we suggest using this feature only for job recovery, 
> while stick with FLINK-11458 for the 
> upgrading/cross-cluster-job-migration/state-backend-switch cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to