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 2022/07/01 13:33:00 UTC
[jira] [Closed] (FLINK-28271) Add configuration options for speculative scheduler
[ https://issues.apache.org/jira/browse/FLINK-28271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu closed FLINK-28271.
---------------------------
Resolution: Done
Done via 2aae49748350806a8523b3b0d95b6f795a9327f0
> Add configuration options for speculative scheduler
> ---------------------------------------------------
>
> Key: FLINK-28271
> URL: https://issues.apache.org/jira/browse/FLINK-28271
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Configuration
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> Following config options are needed for speculative scheduler:
> * jobmanager.adaptive-batch-scheduler.speculative.enabled, default to "false". It controls whether to enable speculative execution. Note that speculative execution only works with AdaptiveBatchScheduler, which requires "jobmanager.scheduler" to be set to "AdaptiveBatch".
> * jobmanager.adaptive-batch-scheduler.speculative.max-concurrent-executions, default to "2". It controls how many executions (including the original one and speculative ones) of an ExecutionVertex can execute at the same time.
> * jobmanager.adaptive-batch-scheduler.speculative.block-slow-node-duration, default to "1 min". It controls how long an identified slow node should be blocked for.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)