[
https://issues.apache.org/jira/browse/FLINK-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197175#comment-16197175
]
Aljoscha Krettek commented on FLINK-7750:
-----------------------------------------
If the data was not split when using Flink 1.2.x this was only a side-effect of
an optimisation in the state backend that would allow it to not store state in
a file system and instead send it to the job manager.
I'm afraid what you are observing is the expected behaviour.
> 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)
