[
https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kwangin (Dennis) Jung updated FLINK-32716:
------------------------------------------
Summary: Give 'Default'(or maybe 'None') option for 'scheduler-mode' (was:
Give 'None' option for 'scheduler-mode')
> Give 'Default'(or maybe 'None') option for 'scheduler-mode'
> -----------------------------------------------------------
>
> Key: FLINK-32716
> URL: https://issues.apache.org/jira/browse/FLINK-32716
> Project: Flink
> Issue Type: Improvement
> Reporter: Kwangin (Dennis) Jung
> Priority: Minor
>
> By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing
> status.
> [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options]
> But currently it only allows 'REACTIVE', and when I want to de-activate with
> such value as 'None', it causes exception.
> (For now, it causes exception if I setup any other value instead of
> 'REACTIVE')
>
> To make configuration bit more flexible, how about give 'None' (or 'Default')
> as an option, to run in default mode?
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
