You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias (Jira)" <ji...@apache.org> on 2020/08/28 10:00:00 UTC
[jira] [Commented] (FLINK-10429) Redesign Flink Scheduling,
introducing dedicated Scheduler component
[ https://issues.apache.org/jira/browse/FLINK-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186438#comment-17186438 ]
Matthias commented on FLINK-10429:
----------------------------------
Hi [~zhuzh], I looked at this issue as part of the Engine team's backlog grooming. It appears that we're still waiting for FLINK-15626 and FLINK-16430 to done. Is this still the case or are there some updates on finishing this ticket?
> 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: Runtime / Coordination
> Affects Versions: 1.7.0
> Reporter: 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
(v8.3.4#803005)