J茅r么me Gagnon
06/05/2024, 5:38 PMMaxim Senin
06/05/2024, 7:55 PMjob.autoscaler.scale-up.max-factor to 6-10 to scale up faster when workload increases. To react to workload increase faster you may need to adjust your job.autoscaler.metrics.window to shorter interval.
I'm actually facing an opposite problem - it doesn't scale down when workload is 0 after all pending records had been processed. I'm not sure if the problem is due to job.autoscaler.scaling.effectiveness.detection.enabled= true or job.autoscaler.restart.time-tracking.enabled=true -- maybe it tried once and then saw that it's taking too long so not worth scaling down, or may be there was an error on scaledown and it rolled back to the last known good parallelism due to kubernetes.operator.deployment.rollback.enabled=trueMaxim Senin
06/05/2024, 7:55 PMJ茅r么me Gagnon
06/05/2024, 8:01 PMMaxim Senin
06/05/2024, 8:02 PMJ茅r么me Gagnon
06/05/2024, 8:03 PMMaxim Senin
06/05/2024, 9:49 PMhearbeat.timeout - I see a lot of job restarts due to that value being too low and causing an error, especially when there are dozens or 100+ task nodes, at least in my environment.