Aljoscha Krettek commented on FLINK-8753:

I don't think we can do this currently. Savepoints have the nice property that 
they are self-contained, which we would loose by making them incremental. Also, 
there is a rough plan to unify the format of savepoints between the different 
state backends and allowing RocksDB incremental savepoints, which probably have 
a similar format to normal RocksDB incremental checkpoints would move us very 
far from that goal. Lastly, making savepoints incremental means that they have 
to be integrated with the bookkeeping of shared state handles, which seems very 
hard to do.

> Introduce Incremental savepoint
> -------------------------------
>                 Key: FLINK-8753
>                 URL: https://issues.apache.org/jira/browse/FLINK-8753
>             Project: Flink
>          Issue Type: New Feature
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.5.0
>            Reporter: Sihua Zhou
>            Assignee: Sihua Zhou
>            Priority: Major
> Right now, savepoint goes through the full checkpoint path, take a savepoint 
> could be slowly. In our production, for some long term job it often costs 
> more than 10min to complete a savepoint which is unacceptable for a real time 
> job, so we have to turn back to use the externalized checkpoint instead 
> currently. But the externalized  checkpoint has a time interval (checkpoint 
> interval) between the last time. So I proposal to introduce the increment 
> savepoint which goes through the increment checkpoint path.
> Any advice would be appreciated!

This message was sent by Atlassian JIRA

Reply via email to