[
https://issues.apache.org/jira/browse/FLINK-16430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhu Zhu closed FLINK-16430.
---------------------------
Release Note: Beginning from Flink 1.12, jobs will be scheduled in the unit
of pipelined regions. A pipelined region is a set of pipelined connected tasks.
This means that, for streaming jobs which consist of multiple regions, it no
longer waits for all tasks to acquire slots before starting to deploy tasks.
Instead, any region can be deployed once it has acquired enough slots for
within tasks. For batch jobs, tasks will not be assigned slots and get deployed
individually. Instead, a task will be deployed together with all other tasks in
the same region, once the region has acquired enough slots.
Resolution: Done
> FLIP-119 Pipelined Region Scheduling
> ------------------------------------
>
> Key: FLINK-16430
> URL: https://issues.apache.org/jira/browse/FLINK-16430
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Fix For: 1.12.0
>
>
> Pipelined region scheduling is targeting to allow batch jobs with PIPELINED
> data exchanges to run without the risk to encounter a resource deadlock.
> More details see
> [FLIP-119|https://cwiki.apache.org/confluence/display/FLINK/FLIP-119+Pipelined+Region+Scheduling]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
