-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[observability][autoscaler] Ensure pending nodes is reset to 0 after scaling #32085
[observability][autoscaler] Ensure pending nodes is reset to 0 after scaling #32085
Conversation
cc @gvspraveen |
{ | ||
"autoscaler_cluster_resources": 0, | ||
"autoscaler_pending_resources": 0, | ||
"autoscaler_pending_nodes": 0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any way to write a test that could've caught this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this precisely a test that catches this?
Remaining test failures look unrelated/flakey. merging |
…scaling (ray-project#32085) The previous way pending_nodes was calculated was prone to race conditions, instead, let's just always publish it in the main thread with other metrics. Closes ray-project#31982 --------- Co-authored-by: Alex <[email protected]> Signed-off-by: Edward Oakes <[email protected]>
Why are these changes needed?
The previous way pending_nodes was calculated was prone to race conditions, instead, let's just always publish it in the main thread with other metrics.
Related issue number
Closes #31982
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.