-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Autoscaler Policy Overrides Count each time a job is deployed #9839
Comments
Hi @idrennanvmware. When Testing this locally I got the behaviour you desire with the following steps:
I hope this helps. Please let me know if you have any follow up questions or comments. |
@jrasell - thank you! I had no idea about the Thanks again |
resolves hashicorp#9839 resolves hashicorp#6929 resolves hashicorp#6910 e2e: template env interpolation path testing
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Output from
nomad version
1.0.2
Issue
First, apologies if this is in the wrong repo. I wasn't sure if this fell under Nomad, or the Nomad autoscaler.
We have been experimenting with the scaling stanza in preparation for some work around the Autoscaling feature(s) in Nomad. In our work we found some behavior we didn't expect around the scaling stanza - we found that that our CI/CD pipeline would deploy Nomad jobs (due to other changes) but the count of the job would always revert to the MIN of the scaling stanza. We tried omitting the
count
at the group level as well as setting it - both scenarios had undesirable results. If we set acount
for the group then the job would always get set to that, regardless of any scaling that had been applied. We weren't sure if this was due to us havingenabled = false
(which is actually what we want as we're using the UI to manually scale groups while we experiment.Reproduction steps
Deploy the job
Scale the job group to 2 in the UI
Deploy the original job file (again)
Job scales back to the original count of 1.
The text was updated successfully, but these errors were encountered: