[jira] [Comment Edited] (FLINK-32716) Give 'None' option for 'scheduler-mode'

[Kwangin (Dennis) Jung (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750517#comment-17750517
 ] 

Kwangin (Dennis) Jung edited comment on FLINK-32716 at 8/5/23 1:10 AM:
---

[~paul8263] thanks for comment!

I'm currently working on it. If it's okay please review the work when ready  :)

But seems I need to wait to be assigned...


was (Author: JIRAUSER301448):
[~paul8263] thanks for comment!

I'm currently working on it. If it's okay please review the work when ready  :)

> Give '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)

[jira] [Comment Edited] (FLINK-32716) Give 'None' option for 'scheduler-mode'

[Yao Zhang (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750514#comment-17750514
 ] 

Yao Zhang edited comment on FLINK-32716 at 8/3/23 1:09 AM:
---

Hi [~kination],

I got the same problem. Currently I am working on automatic Flink configuration 
and got the same annoying issue. The only legal value is 'reactive'. If we want 
to remain the default value, we have to complelely remove its configuration key.

For each configuration key there might be 3 statuses:
1. Not presented.
2. Set as the default value.
3. Set as other value.

Now for some keys we cannot use status 2 to set the defaul value. It may cause 
inconsistency in configuration.

I think for all flink configurations, there should be a way to remaining their 
default values while keeping their keys listed in the configuration file.

Are you currently working on it? If not I would like to take this issue.

Thanks.


was (Author: paul8263):
Hi [~kination],

I got the same problem. Currently I am working on automatic Flink configuration 
and got the same annoying issue. The only legal value is 'reactive'. If we want 
to remain the default value, we have to complelely remove its configuration key.

For each configuration key there might be 3 statuses:
1. Not presented.
2. Set as the default value.
3. Set as other value.

Now for some keys we cannot use status 2 to set the defaul value. It may cause 
inconsistency in configuration.

I think for all flink configurations, there should be a way to remaining their 
default values while keeping their keys listed in the configuration file.

Are you currently working on this. If not I would like to take this issue.

Thanks.

> Give '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.
> To make configuration bit more flexible, how about give 'None' (or 'Default') 
> as an option, to run in default mode?
> (For now, it causes exception if I setup any other value instead of 
> 'REACTIVE')
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)