[
https://issues.apache.org/jira/browse/FLINK-15626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019254#comment-17019254
]
Zhu Zhu commented on FLINK-15626:
---------------------------------
cc [~trohrmann] [~gjy]
> 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
> Priority: Critical
> Labels: Umbrella
> Fix For: 1.11.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 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
> 3. remove legacy FailoverStrategy, RestartStrategy and utils
> 4. 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)
