[
https://issues.apache.org/jira/browse/FLINK-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363810#comment-15363810
]
ramkrishna.s.vasudevan commented on FLINK-3397:
-----------------------------------------------
[~uce]
As per the suggestion I have already started working on a doc. I will try to
list out how things are working now and may be that we can use to see if all
the current relationship between savepoints and checkpoints are captured. And
you can also add your ideas to it. If the task is a bigger one can split up the
tasks and I can see which one I can take up. [~uce] - your thoughts?
> 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)
