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-4814) Remove extra storage location for externalized checkpoint metadata
Date Mon, 28 Nov 2016 12:47:58 GMT

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

ASF GitHub Bot commented on FLINK-4814:

Github user uce commented on the issue:

    @StephanEwen Do you have time to look at this? This exposes the checkpoint directories
via the state backend and let's the JobManager use that one for checkpoint directory configurations.

> Remove extra storage location for externalized checkpoint metadata
> ------------------------------------------------------------------
>                 Key: FLINK-4814
>                 URL: https://issues.apache.org/jira/browse/FLINK-4814
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Ufuk Celebi
> Follow up for FLINK-4512.
> Store checkpoint meta data in checkpoint directory.  That makes it simpler for users
to track and clean up checkpoints manually, if they want to retain externalized checkpoints
across cancellations and terminal failures.
> Every state backend needs to be able to provide a storage location for the checkpoint
metadata. The memory state backend would hence not work with externalized checkpoints, unless
one sets explicitly a parameter `setExternalizedCheckpointsLocation(uri)`.

This message was sent by Atlassian JIRA

View raw message