[
https://issues.apache.org/jira/browse/FLINK-17016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhu Zhu updated FLINK-17016:
----------------------------
Description:
-The PipelinedRegionSchedulingStrategy should be used to schedule Blink planner
batch jobs.
Blink planner batch jobs currently corresponds to
{{ScheduleMode.LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}}.
The SchedulingStrategy loading must be reworked on this mode.-
This task is to enable PipelinedRegionSchedulingStrategy. A config option
"jobmanager.scheduler.scheduling-strategy" should be introduced to control
whether to use the new "region" scheduling or to use the "legacy"
eager/lazy-from-sources scheduling.
If it can pass all required verifications, we can make the new scheduling
strategy the default strategy.
Required verifications are:
1. CI, including all UT/IT cases and E2E tests
2. stability tests
3. TPC-DS benchmark
was:
The PipelinedRegionSchedulingStrategy should be used to schedule Blink planner
batch jobs.
Blink planner batch jobs currently corresponds to
{{ScheduleMode.LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}}.
The SchedulingStrategy loading must be reworked on this mode.
E2E tests are needed to verify this change.
> Enable PipelinedRegionSchedulingStrategy
> ----------------------------------------
>
> Key: FLINK-17016
> URL: https://issues.apache.org/jira/browse/FLINK-17016
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> -The PipelinedRegionSchedulingStrategy should be used to schedule Blink
> planner batch jobs.
> Blink planner batch jobs currently corresponds to
> {{ScheduleMode.LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}}.
> The SchedulingStrategy loading must be reworked on this mode.-
> This task is to enable PipelinedRegionSchedulingStrategy. A config option
> "jobmanager.scheduler.scheduling-strategy" should be introduced to control
> whether to use the new "region" scheduling or to use the "legacy"
> eager/lazy-from-sources scheduling.
> If it can pass all required verifications, we can make the new scheduling
> strategy the default strategy.
> Required verifications are:
> 1. CI, including all UT/IT cases and E2E tests
> 2. stability tests
> 3. TPC-DS benchmark
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
