You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2019/09/24 09:08:00 UTC

[jira] [Resolved] (FLINK-14145) getLatestCheckpoint(true) returns wrong checkpoint

     [ https://issues.apache.org/jira/browse/FLINK-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora resolved FLINK-14145.
--------------------------------
    Resolution: Fixed

> getLatestCheckpoint(true) returns wrong checkpoint
> --------------------------------------------------
>
>                 Key: FLINK-14145
>                 URL: https://issues.apache.org/jira/browse/FLINK-14145
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Checkpointing
>    Affects Versions: 1.9.0
>            Reporter: Ufuk Celebi
>            Assignee: Gyula Fora
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: 0001-FLINK-14145-runtime-Add-getLatestCheckpoint-test.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The flag to prefer checkpoints for recovery introduced in FLINK-11159 returns the wrong checkpoint if:
> * checkpoints are preferred  ({{getLatestCheckpoint(true)}}),
> * the latest checkpoint is *not* a savepoint,
> * more than a single checkpoint is retained.
> The current implementation assumes that the latest checkpoint is a savepoint and skips over it. I attached a patch for {{StandaloneCompletedCheckpointStoreTest}} that demonstrates the issue.
> You can apply the patch via {{git am -3 < *.patch}}.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)