Skip to content
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

Force refresh before IncreaseSize #116

Merged

Conversation

domenicbozzuto
Copy link

@domenicbozzuto domenicbozzuto commented Jun 24, 2024

Adds an option AZURE_VMSS_CACHE_FORCE_REFRESH to force the refresh of the VMSS cache (not VMSS VMs cache per scale set) before an upscale is triggered. This ensures that the size that will be considered during the upscale is up to date, and minimizes the potential for skew in accounting by relying on scaleSet.curSize.

This also adds a check and some more logging on the upscale path to ensure that an 'upscale' to a size that's lower than the current size is never attempted, as this would always delete random instances.

@domenicbozzuto domenicbozzuto force-pushed the dom.bozzuto/azure-force-refresh-on-scaleup branch from 4461ff2 to 6c8a68e Compare June 25, 2024 14:07
@domenicbozzuto domenicbozzuto marked this pull request as ready for review June 25, 2024 14:16
@domenicbozzuto domenicbozzuto force-pushed the dom.bozzuto/azure-force-refresh-on-scaleup branch from 6c8a68e to 00e7281 Compare June 25, 2024 14:17
@domenicbozzuto domenicbozzuto force-pushed the dom.bozzuto/azure-force-refresh-on-scaleup branch from 00e7281 to 15f6d76 Compare June 25, 2024 19:18
@domenicbozzuto domenicbozzuto merged commit bada18d into datadog-master-12.0 Jun 27, 2024
6 checks passed
@domenicbozzuto domenicbozzuto deleted the dom.bozzuto/azure-force-refresh-on-scaleup branch June 27, 2024 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants