[
https://issues.apache.org/jira/browse/FLINK-30574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-30574.
------------------------------
Fix Version/s: kubernetes-operator-1.4.0
Resolution: Fixed
merged to main ed6acd453c6e14f7fdb3295c6f0d0567de6acbd8
> Do not scale further up if last scaling was ineffective
> -------------------------------------------------------
>
> Key: FLINK-30574
> URL: https://issues.apache.org/jira/browse/FLINK-30574
> Project: Flink
> Issue Type: New Feature
> Components: Autoscaler, Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.4.0
>
>
> Related to https://issues.apache.org/jira/browse/FLINK-30571 but somewhat
> simpler.
> It should be easy to detect when a scale up operation did not significantly
> increase the parallelism (or even deteriorated it). In these cases it is very
> important to not try to scale further.
> This can happen if the job hit some external limit (such as rate limiting on
> an external service) or if the performance problems are caused by other
> factors such as memory.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
