[jira] [Updated] (FLINK-31936) Support setting scale up max factor
[ https://issues.apache.org/jira/browse/FLINK-31936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31936: --- Fix Version/s: kubernetes-operator-1.5.0 > Support setting scale up max factor > --- > > Key: FLINK-31936 > URL: https://issues.apache.org/jira/browse/FLINK-31936 > Project: Flink > Issue Type: Improvement > Components: Autoscaler >Reporter: Zhanghao Chen >Assignee: Zhanghao Chen >Priority: Major > Labels: pull-request-available > Fix For: kubernetes-operator-1.5.0 > > > Currently, only scale down max factor is supported to be configured. We > should also add a config for scale up max factor as well. In many cases, a > job's performance won't improve after scaling up due to external bottlenecks. > Although we can detect ineffective scaling up and would block further > scaling, but it already hurts if we scale too much in a single step which may > even burn out external services. > As for the default value, I think 200% would be a good start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31936) Support setting scale up max factor
[ https://issues.apache.org/jira/browse/FLINK-31936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-31936: --- Labels: pull-request-available (was: ) > Support setting scale up max factor > --- > > Key: FLINK-31936 > URL: https://issues.apache.org/jira/browse/FLINK-31936 > Project: Flink > Issue Type: Improvement > Components: Autoscaler >Reporter: Zhanghao Chen >Assignee: Zhanghao Chen >Priority: Major > Labels: pull-request-available > > Currently, only scale down max factor is supported to be configured. We > should also add a config for scale up max factor as well. In many cases, a > job's performance won't improve after scaling up due to external bottlenecks. > Although we can detect ineffective scaling up and would block further > scaling, but it already hurts if we scale too much in a single step which may > even burn out external services. > As for the default value, I think 200% would be a good start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31936) Support setting scale up max factor
[ https://issues.apache.org/jira/browse/FLINK-31936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhanghao Chen updated FLINK-31936: -- Description: Currently, only scale down max factor is supported to be configured. We should also add a config for scale up max factor as well. In many cases, a job's performance won't improve after scaling up due to external bottlenecks. Although we can detect ineffective scaling up and would block further scaling, but it already hurts if we scale too much in a single step which may even burn out external services. As for the default value, I think 200% would be a good start. was: Currently, only scale down max factor is supported to be configured. We should also add a config for scale up max factor as well. In many cases, a job's performance won't improve after scaling up due to external bottlenecks. Although we can detect ineffective scaling up would block further scaling, but it already hurts if we scale too much in a single step which may even burn out external services. As for the default value, I think 200% would be a good start. > Support setting scale up max factor > --- > > Key: FLINK-31936 > URL: https://issues.apache.org/jira/browse/FLINK-31936 > Project: Flink > Issue Type: Improvement > Components: Autoscaler >Reporter: Zhanghao Chen >Priority: Major > > Currently, only scale down max factor is supported to be configured. We > should also add a config for scale up max factor as well. In many cases, a > job's performance won't improve after scaling up due to external bottlenecks. > Although we can detect ineffective scaling up and would block further > scaling, but it already hurts if we scale too much in a single step which may > even burn out external services. > As for the default value, I think 200% would be a good start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31936) Support setting scale up max factor
[ https://issues.apache.org/jira/browse/FLINK-31936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhanghao Chen updated FLINK-31936: -- Description: Currently, only scale down max factor is supported to be configured. We should also add a config for scale up max factor as well. In many cases, a job's performance won't improve after scaling up due to external bottlenecks. Although we can detect ineffective scaling up would block further scaling, but it already hurts if we scale too much in a single step which may even burn out external services. As for the default value, I think 200% would be a good start. was:Currently, only scale down max factor is supported to be configured. We should also add a config for scale up max factor as well. In many cases, a job's performance won't improve after scaling up due to external bottlenecks. Although we can detect ineffective scaling up would block further scaling, but it already hurts if we scale too much in a single step which may even burn out external services. > Support setting scale up max factor > --- > > Key: FLINK-31936 > URL: https://issues.apache.org/jira/browse/FLINK-31936 > Project: Flink > Issue Type: Improvement > Components: Autoscaler >Reporter: Zhanghao Chen >Priority: Major > > Currently, only scale down max factor is supported to be configured. We > should also add a config for scale up max factor as well. In many cases, a > job's performance won't improve after scaling up due to external bottlenecks. > Although we can detect ineffective scaling up would block further scaling, > but it already hurts if we scale too much in a single step which may even > burn out external services. > As for the default value, I think 200% would be a good start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
