[
https://issues.apache.org/jira/browse/FLINK-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187987#comment-16187987
]
Razvan commented on FLINK-7750:
-------------------------------
[~aljoscha] Hi, it's on the local disk of the JobManager whre I'm running the
command from. But as I told it will only save the _metadata in this location
and for the savepoint it will create the same folder location but on the
TaskManager where the job is currently running. So I cannot use any of the
locations to restore, I would need to copy all this to one folder and use that.
With 1.2.0 it didn't split it like this, all could be found on the Jobmanager.
(With distributed FS S3 works fine)
> Strange behaviour in savepoints
> -------------------------------
>
> Key: FLINK-7750
> URL: https://issues.apache.org/jira/browse/FLINK-7750
> Project: Flink
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.3.2
> Reporter: Razvan
> Priority: Blocker
>
> I recently upgraded from 1.2.0 and savepoint creration behaves strange.
> Whenever I try to create a savepoint with specified directory Apache Flink
> creates a folder on the active JobManager (even if I trigger savepoint
> creation from a different JobManager) which contains only _metadata. And
> another folder on the TaskManager where the job is running which contains the
> actual savepoint.
> Obviously if I try to restore it says it can't find the savepoint.
> This worked in 1.2.0.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
