You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Elias Levy (JIRA)" <ji...@apache.org> on 2017/09/13 18:58:02 UTC

[jira] [Commented] (FLINK-4814) Remove extra storage location for externalized checkpoint metadata

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

Elias Levy commented on FLINK-4814:
-----------------------------------

Wondering what is the status of this?  The current state, as pointed out in FLINK-5627, is quite odd.  You can configure the checkpoint directory programmatically, but not the externalized checkpoint directory.  Will it make it into 1.4?

> 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
>          Components: State Backends, Checkpointing
>            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
(v6.4.14#64029)