[
https://issues.apache.org/jira/browse/FLINK-21450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751793#comment-17751793
]
Konstantin Knauf commented on FLINK-21450:
------------------------------------------
[~roman] I think, we still need to update the documentation/limitations on
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/elastic_scaling/,
right?
> 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)
