[
https://issues.apache.org/jira/browse/FLINK-28473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564903#comment-17564903
]
ming li edited comment on FLINK-28473 at 7/11/22 9:51 AM:
----------------------------------------------------------
[~chesnay], at present, after JM failover, all tasks must be restarted. Can we
record the previous allocation as [~lkokhreidze] said? Going further, maybe the
[Flink-7641|https://issues.apache.org/jira/browse/FLINK-7641] is a more ideal
workaround.
was (Author: ming li):
[~chesnay], at present, after JM failover, all tasks must be restarted. Can we
record the previous allocation as [~lkokhreidze] said? Going further, maybe the
Flink-7641 is a more ideal workaround.
> JobManager restart/failover doesn't trigger local recovery on TaskManagers
> --------------------------------------------------------------------------
>
> Key: FLINK-28473
> URL: https://issues.apache.org/jira/browse/FLINK-28473
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends, Runtime / Task
> Affects Versions: 1.15.0, 1.15.1
> Reporter: Levani Kokhreidze
> Priority: Major
>
> Hi! While experimenting with local recovery feature (Flink 1.15.1) I noticed
> that if JobManager is restarted TaskManagers always recover from Remote
> ({{{}IncrementalRemoteKeyedStateHandle{}}}). While if I restart task
> managers, local recovery is triggered.
>
> Setup: * HA setup with Zookeeper and S3 remote storage.
> * JobManager runs as StatefulSet with PersistentVolume. Both
> {{process.jobmanager.working-dir}} and {{jobmanager.resource-id}} are
> correctly configured.
> * TaskManagers run as StatefulSets with PersistentVolume. Both
> {{process.taskmanager.working-dir}} and {{taskmanager.resource-id}} are
> correctly configured.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
