[
https://issues.apache.org/jira/browse/FLINK-25952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz closed FLINK-25952.
------------------------------------
Resolution: Fixed
Fixed in:
* master
** 27cd145cbf5a694aa81419e2472c9da84e137cfa
* 1.14.4
** e2a17adf9075ba5feb99a5c87a1b8d41254bbe9e
* 1.13.7
** e12ad75f0ecf364e9c99aa0ddc42c4dd0475c1b4
> Savepoint on S3 are not relocatable even if entropy injection is not enabled
> ----------------------------------------------------------------------------
>
> Key: FLINK-25952
> URL: https://issues.apache.org/jira/browse/FLINK-25952
> Project: Flink
> Issue Type: Bug
> Components: FileSystems, Runtime / Checkpointing
> Affects Versions: 1.15.0, 1.13.5, 1.14.3
> Reporter: Dawid Wysakowicz
> Assignee: Dawid Wysakowicz
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.15.0, 1.14.4, 1.13.7
>
>
> We have a limitation that if we create savepoints with an injected entropy,
> they are not relocatable
> (https://nightlies.apache.org/flink/flink-docs-master/docs/ops/state/savepoints/#triggering-savepoints).
> However the check if we use the entropy is flawed. In
> {{FsCheckpointStreamFactory}} we check only if the used filesystem extends
> from {{EntropyInjectingFileSystem}}. {{FlinkS3FileSystem}} does, but it still
> may have the entropy disabled. {{FlinkS3FileSystem#getEntropyInjectionKey}}
> may still return {{null}}. We should check for that in
> {{org.apache.flink.core.fs.EntropyInjector#isEntropyInjecting}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
