You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2016/06/23 05:56:16 UTC

[jira] [Commented] (FLINK-3397) Failed streaming jobs should fall back to the most recent checkpoint/savepoint

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

ramkrishna.s.vasudevan commented on FLINK-3397:
-----------------------------------------------

Can I take this up?  Planning to read the code and then see if I can try out a patch here? Any suggestion/feedback [~gyfora]?

> 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: 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)