You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/08/28 12:05:00 UTC
[jira] [Closed] (FLINK-14234) All partition consumable events
should be notified to SchedulingStrategy (SchedulerNG)
[ https://issues.apache.org/jira/browse/FLINK-14234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu closed FLINK-14234.
---------------------------
Resolution: Won't Do
Not a must at the moment so close it for now.
> All partition consumable events should be notified to SchedulingStrategy (SchedulerNG)
> --------------------------------------------------------------------------------------
>
> Key: FLINK-14234
> URL: https://issues.apache.org/jira/browse/FLINK-14234
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{SchedulingStrategy}} requires partition consumable notification to make scheduling decisions.
> According to {{SchedulingStrategy#onPartitionConsumable}} definition, all partition consumable events should be notified to {{SchedulingStrategy}}, including those from TMs (pipelined partitions consumable for data produced) and from within JM(blocking partitions consumable for producer finished).
> In this way, the LazyFromSourcesSchedulingStrategy does not need to maintain the result partition status by itself. InputDependencyConstraintChecker can be simplified a lot in this way.
> Besides that, LazyFromSourcesSchedulingStrategy does not need to be aware of result partition types(PIPELINED/BLOCKING) in this way.
> It would also simplify the input checking for pipelined region scheduling.
> More details see [here|https://github.com/apache/flink/pull/9663#discussion_r326540913].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)