[3.x] Scale to the maxProcesses if timeToClearAll is zero #718
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
driesvints
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref: #667
When you first start Horizon, before finishing any jobs, the
timeToClearAllwill be equal to zero. This will make Horizon scale down to theminProcessesset on the supervisor.Once your first job finishes,
timeToClearAllwill start having values that the auto scaler can use to decide if it should scale up or down.The problem is that before finishing any jobs, even if you have 10 jobs waiting, Horizon will scale down to
minProcessesbecausetimeToClearAllis still zero.This PR changes the behaviour by checking if there are any jobs waiting and only scale down if there aren't any.