kfaraz commented on PR #20708: URL: https://github.com/apache/druid/pull/20708#issuecomment-6460439549
>> Once a taskCount has been chosen, commit to it and let it become stable. > Here where my concern is risen. Do we want to commit to unlucky choice at the beginning, while the general design should be tied to [task amount] cost-efficiency? @Fly-Style , we commit to a given taskCount only until the next minScaleUpDelay or minScaleDownDelay or taskDuration elapses. In other words, there is no change in this aspect. Sorry for the confusion. By commit, I only meant that the next time when we do a scale action, we evaluate the _overall_ impact of the last choice for however long it has run instead of just the latest metrics (which shows the picture for only the last minute or less). Thus we avoid half baked decisions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
