[
https://issues.apache.org/jira/browse/FLINK-33770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-33770:
-----------------------------------
Labels: pull-request-available (was: )
> Autoscaler logs are full of deprecated key warnings
> ---------------------------------------------------
>
> Key: FLINK-33770
> URL: https://issues.apache.org/jira/browse/FLINK-33770
> Project: Flink
> Issue Type: Bug
> Components: Autoscaler, Kubernetes Operator
> Affects Versions: kubernetes-operator-1.7.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.8.0
>
>
> We moved all autoscaler configuration from
> {{kubernetes.operator.job.autoscaler.*}} to {{job.autoscaler.*}}.
> With the latest release, the logs are full with logs like this:
> {noformat}
> level: WARN
> logger: org.apache.flink.configuration.Configuration
> message: Config uses deprecated configuration key
> 'kubernetes.operator.job.autoscaler.target.utilization' instead of proper key
> 'job.autoscaler.target.utilization'
> {noformat}
> The reason is that the configuration is loaded for every reconciliation.
> This configuration is already widely adopted across hundreds of pipelines. I
> propose to remove the deprecation from the config keys and make them
> "fallback" keys instead which removes the deprecation warning.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
