You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/01/02 10:15:00 UTC

[jira] [Updated] (FLINK-33965) Refactor the configuration for autoscaler standalone

     [ https://issues.apache.org/jira/browse/FLINK-33965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-33965:
-----------------------------------
    Labels: pull-request-available  (was: )

> Refactor the configuration for autoscaler standalone
> ----------------------------------------------------
>
>                 Key: FLINK-33965
>                 URL: https://issues.apache.org/jira/browse/FLINK-33965
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Rui Fan
>            Assignee: Rui Fan
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, all configurations of autoscaler standalone are maintained in string key.
> When autoscaler standalone has a little options, it's easy to maintain. However, I found it's hard to maintain when we add more options.
> During I developing the JDBC autoscaler state store and control loop supports multiple thread. It will introduce more options.
> h2. Solution:
> Introducing the AutoscalerStandaloneOptions to manage all options of autoscaler standalone. And output the doc for it.



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