Hi, does that mean https://issues.apache.org/jira/browse/FLINK-5627 <https://issues.apache.org/jira/browse/FLINK-5627> is no longer relevant for you, since it seems to request the behaviour that we have now?
But yes, I think it's currently not possible (with out-of-box functionality) to write externalized-checkpoint metadata to a central location. There is this Jira issue which aims at implementing a solution: https://issues.apache.org/jira/browse/FLINK-9114 <https://issues.apache.org/jira/browse/FLINK-9114>. I quickly talked to Stephan, it seems to be that the meta info about externalized checkpoints is also written to the HA storage directory, maybe that's helpful for you. Best, Aljoscha > On 12. Jul 2018, at 14:18, Gyula Fóra <gyula.f...@gmail.com> wrote: > > Hi, > It seems that the behaviour to store the checkpoint metadata files for > externalized checkpoints changed from 1.4 to 1.5 and the docs seem to be > incorrectly saying that: > "state.checkpoints.dir: The target directory for meta data of externalized > checkpoints > <https://ci.apache.org/projects/flink/flink-docs-release-1.5/ops/state/checkpoints.html#externalized-checkpoints>" > > Now the external metadata files simply end up in the checkpoint dir as > configured in the state backend so basically the "state.checkpoints.dir" > param is overwritten by the job. This breaks a bunch of tooling around > checkpoints that rely on a common place for metadata files instead of > scattered around in subdirectories. I wonder is there any way to get the > previous behaviour back? > > Thanks, > Gyula
