Closed yuriy-filatov closed 2 years ago
The flag is present as a query param on the scale request. See https://github.com/HubSpot/Singularity/blob/3b120a92c304c659cd894b1f790f8b10378db991/SingularityService/src/main/java/com/hubspot/singularity/resources/RequestResource.java#L1786 adn the deploy resource, if executing a deploy that changes scale. It is also present as a checkbox in the UI if scaling via UI, or as an argument on the Singularity java client if scaling via api
Thanks @ssalinas Is there a global toggle in s9y server config I can bump to override defaults, i.e. set default to 50 instances or allow largeScaleDown? Usecase is -- we have a running deployment with 50 job instances and trying to 'update' it through our ci/cd -- but get the error above.
If you want to effectively turn off the check, you can set maxScaleDownWithoutAcknowledgement
at the base of the yaml to a much larger number. Default is 10. Alternatively, just acknowledge by setting the value to true on the scale/deploy api calls
Thanks, we'll give it a try.
Works for us with global override, thanks.
Currently we're stuck with
I've tried to add
largeScaleDownAcknowledged=true
to s9y request section in the job's yaml -- but no luck. Can you please explain how to use this toggle? Thanks.