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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

Shang Yuanchun (Jira)
Zhu Zhu created FLINK-20439:
-------------------------------

             Summary: Consider simplifying or removing mechanism to scheduleOrUpdateConsumers
                 Key: FLINK-20439
                 URL: https://issues.apache.org/jira/browse/FLINK-20439
             Project: Flink
          Issue Type: Sub-task
          Components: Runtime / Coordination
            Reporter: Zhu Zhu
             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)