[ 
https://issues.apache.org/jira/browse/FLINK-35814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865034#comment-17865034
 ] 

Rui Fan commented on FLINK-35814:
---------------------------------

Thanks [~gyfora]  for the reminder!

Sorry, I didn't notice it before. I face this issue due to 
job.autoscaler.scaling.effectiveness.detection.enabled is false by default. I 
will enable job.autoscaler.scaling.effectiveness.detection.enabled and try 
again.

 

Also, could we enable it by default if it works.? This feature is useful, it 
can avoid ineffective scaling. I'm afraid most of users don't know this option, 
and it's better to provide the out-of-box autoscaler for users.

> Don't scale up continuously when the throughout cannot be increased after 
> scaling up
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-35814
>                 URL: https://issues.apache.org/jira/browse/FLINK-35814
>             Project: Flink
>          Issue Type: Improvement
>          Components: Autoscaler
>            Reporter: Rui Fan
>            Assignee: Rui Fan
>            Priority: Major
>
> h2. Motivation
> Currently, the parallelism will be increased continuously when some cases 
> happen. Such as: data skew, bottleneck occurs in other system.
> In these cases, the throughout(processing rate) cannot be increased even if 
> we increase the parallelism.
> h2. Solution
> We don't need to scale up the task continuously when the throughout cannot be 
> increased after scaling up. 
> And it's better to trigger some events to reminder users fix the issue 
> manually.



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

Reply via email to