[
https://issues.apache.org/jira/browse/FLINK-34021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805363#comment-17805363
]
Rui Fan commented on FLINK-34021:
---------------------------------
Merged to main(1.8.0) via : f67cba9c8269ddd4e27fcdc40cfd8a293ae665de
> Print jobKey in the Autoscaler standalone log
> ---------------------------------------------
>
> Key: FLINK-34021
> URL: https://issues.apache.org/jira/browse/FLINK-34021
> Project: Flink
> Issue Type: Sub-task
> Components: Autoscaler
> Affects Versions: kubernetes-operator-1.8.0
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.8.0
>
>
> FLINK-33814 has supported the multiple threads scaling for autoscaler
> standalone. When a lot of jobs are scaling, autoscaler standalone will print
> too many logs. Currently, each log doesn't have the job key, it's hard to
> maintain.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
