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/12/14 11:56:00 UTC

[jira] [Updated] (FLINK-20439) Consider simplifying or removing mechanism to scheduleOrUpdateConsumers

     [ https://issues.apache.org/jira/browse/FLINK-20439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhu Zhu updated FLINK-20439:
----------------------------
        Parent:     (was: FLINK-15626)
    Issue Type: Task  (was: Sub-task)

> Consider simplifying or removing mechanism to scheduleOrUpdateConsumers
> -----------------------------------------------------------------------
>
>                 Key: FLINK-20439
>                 URL: https://issues.apache.org/jira/browse/FLINK-20439
>             Project: Flink
>          Issue Type: Task
>          Components: Runtime / Coordination
>            Reporter: Zhu Zhu
>            Priority: Major
>             Fix For: 1.13.0
>
>
> Execution#scheduleOrUpdateConsumers() was used for multiple purposes:
> - schedule a vertex when its PIPELINED inputs have produced data 
> - schedule a vertex when its BLOCKING inputs have finished
> - update consumed partition info to RUNNING consumers
> - cache consumed partition info for DEPLOYING consumers
> It is not needed anymore in the latest pipelined region scheduling because 
> - a region will be scheduled only when all its upstream regions have finished
> - a vertex will always know all its consumed partitions when scheduled
> So we can consider how to simply or remove it, which also involves things like UnknownInputChannel, ResultPartitionConsumableNotifier, Execution#cachePartitionInfo(), etc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)