flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gyula Fora (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3397) Failed streaming jobs should fall back to the most recent checkpoint/savepoint
Date Thu, 23 Jun 2016 08:52:16 GMT

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

Gyula Fora commented on FLINK-3397:
-----------------------------------

You are always free to give it a shot, to be honest I am not perfectly sure wether other people
are working in this direction. Maybe [~uce] can help me out here as he knows well what's going
on with savepoints...

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

Mime
View raw message