[
https://issues.apache.org/jira/browse/FLINK-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166428#comment-16166428
]
Aljoscha Krettek commented on FLINK-4814:
-----------------------------------------
Yes I think this is still a problem and I think it's part of a larger problem
that I'm trying to address in this one-pager:
https://docs.google.com/document/d/1Q8hkpl2VVXrbEaJkQNe88kuus0F5wFFiebub9hqrg1s/edit?usp=sharing
I'm just laying out what I would like to have, no solutions yet, though. What
do you think?
> 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)
