flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3397) Failed streaming jobs should fall back to the most recent checkpoint/savepoint
Date Wed, 06 Jul 2016 07:54:11 GMT

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

ASF GitHub Bot commented on FLINK-3397:
---------------------------------------

Github user uce commented on the issue:

    https://github.com/apache/flink/pull/2195
  
    Makes sense :-)


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

Mime
View raw message