[FLINK-34311] Do not change min resource requirements when rescaling for adaptive scheduler

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: kubernetes-operator-1.8.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Gyula Fora
• Reporter: Gyula Fora
• Created: 30/Jan/24 13:43
• Updated: 05/Feb/24 14:33
• Resolved: 05/Feb/24 14:33

Description

when applying the rescale api to change parallelism we should not change the min parallelism.
The problem currently is that if we cannot aquire the new resources within jobmanager.adaptive-scheduler.resource-wait-timeout the job will completely fail

The jobmanager.adaptive-scheduler.resource-stabilization-timeout still allows us to wait for quite long if necessary to get the target parallelism but failing completely because of the wait timeout seems very unfortunate

It's best to keep the min resources unchanged and let the adaptive scheduler take care of the parallelism changes together with the timeout settings.

Issue Links

• links to: GitHub Pull Request #763