-
-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support MaxGrowthRate #851
Comments
Valid point. Version 7 adds many parameters. Guess we should add |
Looking forward to this! I'm currently trying a completely on demand approach (idle-count = 0), but runners tend to leave orphaned workers. I think it is because they run out of memory when very big workloads reach them in a very short amount of time (From 0 to 300 jobs leaves some orphaned workers for a 8GB memory runner). Having a |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
…arallel (#962) ## Description This feature allows to support `MaxGrowthRate` which limits the number of instances added in parallel by the Runner. The default of `0` (unlimited) is used if no value is given. The parameter is added to `runner_worker_docker_machine_instance` as this is the only Runner type for which it makes sense. All other types are not able to scale and thus it is not a `runner_worker` parameter. See [advanced-configuration](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnersmachine-section) Closes #851 ## Migrations required NO ## Verification - do not set the parameter --> `MaxGrowthRate` in config file is 0. - set the parameter to any value --> `MaxGrowthRate` in config file is "any value" --------- Co-authored-by: Matthias Kay <github@matthiaskay.de> Co-authored-by: Matthias Kay <matthias.kay@hlag.com>
Describe the solution you'd like
The module already supports parameters like idleCount.
Maybe it should also support MaxGrowthRate: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnersmachine-section
The text was updated successfully, but these errors were encountered: