[
https://issues.apache.org/jira/browse/FLINK-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363160#comment-15363160
]
ASF GitHub Bot commented on FLINK-3397:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/2195
Sorry for not responding earlier in the JIRA issue. I've somehow missed
your mentions. I agree with what Stephan said in JIRA. Before trying to fix
something here, we would have to think about the relationship between
checkpoints and savepoints in general. I also have some other ideas. Is it OK
for you to close this PR for now? Sorry again for not getting back earlier.
> Failed streaming jobs should fall back to the most recent checkpoint/savepoint
> ------------------------------------------------------------------------------
>
> Key: FLINK-3397
> URL: https://issues.apache.org/jira/browse/FLINK-3397
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing, Streaming
> Affects Versions: 1.0.0
> Reporter: Gyula Fora
> Priority: Minor
>
> The current fallback behaviour in case of a streaming job failure is slightly
> counterintuitive:
> If a job fails it will fall back to the most recent checkpoint (if any) even
> if there were more recent savepoint taken. This means that savepoints are not
> regarded as checkpoints by the system only points from where a job can be
> manually restarted.
> I suggest to change this so that savepoints are also regarded as checkpoints
> in case of a failure and they will also be used to automatically restore the
> streaming job.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
