[
https://issues.apache.org/jira/browse/FLINK-21450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830558#comment-17830558
]
Matthias Pohl commented on FLINK-21450:
---------------------------------------
Enabling the tests for AdaptiveScheduler (see FLINK-34409):
* master
**
[8f06fb472ba6a10f0829aecf1eedee26e924aa6d|https://github.com/apache/flink/commit/8f06fb472ba6a10f0829aecf1eedee26e924aa6d]
* 1.19
**
[00492630baa5cf041ea2cce2a3560f3e713bf57a|https://github.com/apache/flink/commit/00492630baa5cf041ea2cce2a3560f3e713bf57a]
* 1.18
**
[f5c243097ac9fae29c3365a2361b7b0c6be3b3ee|https://github.com/apache/flink/commit/f5c243097ac9fae29c3365a2361b7b0c6be3b3ee]
> 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)
