-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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] node caching changes #3937
[autoscaler] node caching changes #3937
Conversation
I don't know if this is a good long term solution, but still fixes the two issues. |
@@ -61,7 +61,7 @@ head_node: | |||
initializeParams: | |||
diskSizeGb: 50 | |||
# See https://cloud.google.com/compute/docs/images for more images |
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.
I updated this example to fix it and match the aws/example-full.yaml
Test FAILed. |
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.
The cache handling looks good. Are the fingerprint fixes also here?
node = self._get_cached_node(node_id) | ||
|
||
if node.public_ip_address is None: | ||
node = self._get_node(node_id) |
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.
+1
Oh I see the change now. |
Co-Authored-By: hartikainen <kristian.hartikainen@gmail.com>
Test PASSed. |
Some lint errors |
Should be fixed now. |
Test PASSed. |
Test PASSed. |
All looks good to me. Apologies; I didn't have an easy way to test on GCP. |
What do these changes do?
Breaks the node provider node getter into cached and non-cached versions.
Related issue number
Closes #3930, Closes #3935