[
https://issues.apache.org/jira/browse/FLINK-15626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271074#comment-17271074
]
Zhu Zhu commented on FLINK-15626:
---------------------------------
[~trohrmann] in the future we may want to factor all the actions out from
ExecutionGraph and its sub-components. But I think we can open a separate task
to do it.
I will close this one as done.
> Remove legacy scheduler
> -----------------------
>
> Key: FLINK-15626
> URL: https://issues.apache.org/jira/browse/FLINK-15626
> Project: Flink
> Issue Type: Task
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Critical
> Labels: Umbrella
> Fix For: 1.13.0
>
>
> This umbrella ticket is to track the tickets to remove the legacy scheduler
> and related components.
> So that we can have a much cleaner scheduler framework which significantly
> simplifies our next development work on job scheduling.
> Here's a rough plan:
> 1. remove LegacyScheduler class
> * related tests should also be removed, including
> AlsoRunWithLegacyScheduler which is used to enable integration tests for
> legacy scheduler
> 2. remove legacy failover strategy AdaptedRestartPipelinedRegionStrategyNG
> and RestartIndividualStrategy. These implementations and their tests heavily
> relies on the legacy scheduling logics in ExecutionGraph so removing them can
> make #3 much easier.
> 3. remove legacy scheduling/failover logics in ExecutionGraph
> * note that many tests still relies on these logics(e.g.
> ExecutionGraph#scheduleForExecution()), we may need to retain and rewrite
> tests which are still needed. So before removing the legacy logics, it's
> better to cleanup all the tests relying on the legacy scheduling first, i.e.
> remove tests that are no needed and rewrite the tests which are still needed.
> 4. remove legacy FailoverStrategy and RestartStrategy
> 5. Factoring out the scheduling logics in ExecutionGraph to make it a plain
> data structure. This can be a long term goal though. There can be several
> pieces and we may need to examine them one by one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
