[
https://issues.apache.org/jira/browse/FLINK-34126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junrui Li updated FLINK-34126:
------------------------------
Component/s: Documentation
(was: Runtime / Configuration)
> Correct the description of jobmanager.scheduler
> -----------------------------------------------
>
> Key: FLINK-34126
> URL: https://issues.apache.org/jira/browse/FLINK-34126
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Reporter: Junrui Li
> Priority: Major
> Labels: pull-request-available
>
> Now the config option jobmanager.scheduler has description:
> _Determines which scheduler implementation is used to schedule tasks.
> Accepted values are:_
> * _'Default': Default scheduler_
> * _'Adaptive': Adaptive scheduler. More details can be found
> [here|https://nightlies.apache.org/flink/flink-docs-master/zh/docs/deployment/elastic_scaling#adaptive-scheduler]._
> * _'AdaptiveBatch': Adaptive batch scheduler. More details can be found
> [here|https://nightlies.apache.org/flink/flink-docs-master/zh/docs/deployment/elastic_scaling#adaptive-batch-scheduler]._
> _Possible values:_
> * _"Default"_
> * _"Adaptive"_
> * _"AdaptiveBatch"_
>
> However, after FLIP-283 we changed the default scheduler for batch job to
> AdaptiveBatchScheduler. This config option description will mislead users
> that the 'DefaultScheduler' is the universal fallback for both batch and
> streaming jobs.
> We should update this description.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
