You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2023/03/02 21:43:00 UTC
[jira] [Resolved] (FLINK-21450) Add local recovery support to adaptive scheduler
[ https://issues.apache.org/jira/browse/FLINK-21450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Khachatryan resolved FLINK-21450.
---------------------------------------
Resolution: Fixed
Merged into master as d718342ad0311ea7481d1a1bd87c395aeff25928..e38a6709b57000e38bf044d0e55da3dd3ec3bde8.
> Add local recovery support to adaptive scheduler
> ------------------------------------------------
>
> Key: FLINK-21450
> URL: https://issues.apache.org/jira/browse/FLINK-21450
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Robert Metzger
> Assignee: Roman Khachatryan
> Priority: Major
> Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned, pull-request-available
> Fix For: 1.18.0
>
>
> local recovery means that, on a failure, we are able to re-use the state in a taskmanager, instead of loading it again from distributed storage (which means the scheduler needs to know where which state is located, and schedule tasks accordingly).
> Adaptive Scheduler is currently not respecting the location of state, so failures require the re-loading of state from the distributed storage.
> Adding this feature will allow us to enable the {{Local recovery and sticky scheduling end-to-end test}} for adaptive scheduler again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)