[jira] (FLINK-32016) Logs are printed as disabled even if the autoscaler option is true

["Tan Kim (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-32016 ]


    Tan Kim deleted comment on FLINK-32016:
    ---------------------------------

was (Author: JIRAUSER300108):
 
{code:java}
# yaml
spec:
  flinkConfiguration:
    execution.checkpointing.interval: 10s
    execution.checkpointing.unaligned: 'false'
    execution.savepoint-restore-mode: NO_CLAIM
    fs.s3a.aws.credentials.provider: com.amazonaws.auth.WebIdentityTokenCredentialsProvider
    high-availability: org.apache.flink.kubernetes.highavailability.KubernetesHaServicesFactory
    high-availability.storageDir: ".."
    kubernetes.hadoop.conf.config-map.name: hadoop-config-common
    kubernetes.operator.job.autoscaler.catch-up.duration: 60m
    kubernetes.operator.job.autoscaler.enabled: 'true'
    kubernetes.operator.job.autoscaler.metrics.busy-time.aggregator: AVG
    kubernetes.operator.job.autoscaler.metrics.window: 5m
    kubernetes.operator.job.autoscaler.restart.time: 5m
    kubernetes.operator.job.autoscaler.scale-down.max-factor: '1'
    kubernetes.operator.job.autoscaler.scale-up.grace-period: 30m
    kubernetes.operator.job.autoscaler.scaling.effectiveness.detection.enabled: 'true'
    kubernetes.operator.job.autoscaler.scaling.sources.enabled: 'true'
    kubernetes.operator.job.autoscaler.stabilization.interval: 5m
    kubernetes.operator.job.autoscaler.target.utilization: '0.7'
    kubernetes.operator.job.autoscaler.target.utilization.boundary: '0.2'
    kubernetes.operator.job.autoscaler.vertex.min-parallelism: '1'
    kubernetes.operator.periodic.savepoint.interval: 1h
    metrics.job.status.enable: STATE
    metrics.reporter.prom.factory.class: org.apache.flink.metrics.prometheus.PrometheusReporterFactory
    pipeline.jobvertex-parallelism-overrides: cbc357ccb763df2852fee8c4fc7d55f2:4
    pipeline.max-parallelism: '120'
    resourcemanager.taskmanager-timeout: '180000'
    restart-strategy: exponential-delay
    restart-strategy.exponential-delay.backoff-multiplier: '2.0'
    restart-strategy.exponential-delay.initial-backoff: 10s
    restart-strategy.exponential-delay.jitter-factor: '0.1'
    restart-strategy.exponential-delay.max-backoff: 120s
    restart-strategy.exponential-delay.reset-backoff-threshold: 600s
    state.backend: rocksdb
    state.backend.incremental: 'true'
    state.checkpoints.dir: ".."
    state.savepoints.dir: ".."
    taskmanager.numberOfTaskSlots: '2'
  flinkVersion: v1_17
  ..


# log
2023-05-06 08:35:24,188 o.a.f.k.o.a.JobAutoScalerImpl  [INFO ][flink-prod/shop-click-streaming-app] Job autoscaler is disabled 
..{code}
 

 

> Logs are printed as disabled even if the autoscaler option is true
> ------------------------------------------------------------------
>
>                 Key: FLINK-32016
>                 URL: https://issues.apache.org/jira/browse/FLINK-32016
>             Project: Flink
>          Issue Type: Improvement
>          Components: Autoscaler
>            Reporter: Tan Kim
>            Priority: Minor
>
> The part where the job.autoscaler.enabled option is logged as disabled due to the code below, even if it is set to true, is misleading to users and needs to be corrected in the log message.
> {code:java}
> if (resource.getSpec().getJob() == null || !conf.getBoolean(AUTOSCALER_ENABLED)) {
>     LOG.info("Job autoscaler is disabled");
>     return false;
> } {code}



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