Fix autoscaler #108
Merged
Fix autoscaler #108
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
88e6ef2 to
52f8760
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains:
A fix in the autoscale logic which did lead to high latency not being recognized. This was a regression introduced while implementing the advanced activity scheduling Better Scheduling/Load Balancing for activities #52.
Improved tracing and error handling for the autoscaler logic. In particular, Netherite logs more information to ETW which makes it easier to use Kusto when debugging auto-scaling related issues.
It may be necessary to propagate these changes to the consumption plan support work currently underway by @bachuv.