[ https://issues.apache.org/jira/browse/FLINK-9983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561655#comment-16561655
]
Aljoscha Krettek commented on FLINK-9983:
-----------------------------------------
See relevant ML thread: https://lists.apache.org/thread.html/5f544062a54a3b3044c63dcb66b1c396a46c9a9adf4d1e6ca11a697c@%3Cuser.flink.apache.org%3E
> Savepoints should count as checkpoints when recovering
> ------------------------------------------------------
>
> Key: FLINK-9983
> URL: https://issues.apache.org/jira/browse/FLINK-9983
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Reporter: Aljoscha Krettek
> Priority: Blocker
> Fix For: 1.6.0
>
>
> If they are not used when recovering you can get intro problems with duplicate output
data when a failure occurs after a savepoint was taken but before the next checkpoint occurs.
> The fix, in the long run, is to differentiate between savepoints that have side effects
and those that don't. The former would be used for a "stop-with-savepoint" scenario while
the latter is for in-between savepoints. This is harder to implement, so I vote for the easy
fix described for now for fixing the duplication problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
|