Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Autoscaler concurrency limiter to avoid overloading #23

Closed
jrasell opened this issue Aug 20, 2019 · 0 comments · Fixed by #24
Closed

Autoscaler concurrency limiter to avoid overloading #23

jrasell opened this issue Aug 20, 2019 · 0 comments · Fixed by #24
Assignees
Labels
area/autoscaling Issues related to internal autoscaling kind/enhancement Issues relating to enhancements

Comments

@jrasell
Copy link
Owner

jrasell commented Aug 20, 2019

Is your feature request related to a problem? Please describe.
Currently the internal autoscaler loops over the stored policies and will trigger and autoscaling run without any limit on the number of concurrent processes. In environments with a decent number of running and scalable jobs, this can cause pressure on the Nomad servers due to the number of API calls required to make.

Describe the solution you'd like.
The autoscaler should have some method to limit the number of concurrent autoscaling activities that can take place. This ideally would be something that has a sensible default, but that can be overridden by the operator. The Nomad num_schedulers provides an ideal reference.

@jrasell jrasell added kind/enhancement Issues relating to enhancements area/autoscaling Issues related to internal autoscaling labels Aug 20, 2019
@jrasell jrasell self-assigned this Aug 20, 2019
jrasell added a commit that referenced this issue Aug 26, 2019
Use goroutine pool within autoscaler to limit concurrency.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/autoscaling Issues related to internal autoscaling kind/enhancement Issues relating to enhancements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant