[
https://issues.apache.org/jira/browse/FLINK-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629769#comment-16629769
]
tison commented on FLINK-10429:
-------------------------------
I like the proposal treat schedule a separated component. It is helpful for
further optimize on scheduling such as FLINK-10240.
To [~zhuzh], [~tiemsn]
I think the first step of the achieve of this redesign would be the extract
part, maybe you can take this document into consideration? Also, the link to
FLINK-10240 is broken, the correct one is
https://docs.google.com/document/d/1zAseuBnqNXg3pst3vLBTc8yGOUo485J2LVWBAdFCW9I/
. And I afraid that it would prevent further discussion that this document is
READ-ONLY, any thought could not be commented on.
For more information, our users start looking for more flexible schedule
strategy. Wish this redesign could help.
> Redesign Flink Scheduling, introducing dedicated Scheduler component
> --------------------------------------------------------------------
>
> Key: FLINK-10429
> URL: https://issues.apache.org/jira/browse/FLINK-10429
> Project: Flink
> Issue Type: New Feature
> Components: Distributed Coordination
> Affects Versions: 1.7.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
>
> This epic tracks the redesign of scheduling in Flink. Scheduling is currently
> a concern that is scattered across different components, mainly the
> ExecutionGraph/Execution and the SlotPool. Scheduling also happens only on
> the granularity of individual tasks, which make holistic scheduling
> strategies hard to implement. In this epic we aim to introduce a dedicated
> Scheduler component that can support use-case like auto-scaling,
> local-recovery, and resource optimized batch.
> The design for this feature is developed here:
> https://docs.google.com/document/d/1q7NOqt05HIN-PlKEEPB36JiuU1Iu9fnxxVGJzylhsxU/edit?usp=sharing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
