-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
AWS DescribeAutoScalingGroups requests too aggressive - API limits reached #422
Conversation
on a side note, I have a mac, and it seems even if I set my GOOS to linux, I am having issues building/testing locally using the master as my baseline. See below: mmerrillmbp:cluster-autoscaler mmerrill$ go version Update, I see #325 and this is no longer an issue. |
@mmerrill3 Can you squash your commits and add a comment once this is ready for review? Thanks. |
29f2d93
to
c7cafdf
Compare
@MaciekPytel, the commits are squashed and this is ready for a review. |
@@ -57,6 +57,9 @@ type CloudProvider interface { | |||
// GetResourceLimiter returns struct containing limits (max, min) for resources (cores, memory etc.). | |||
GetResourceLimiter() (*ResourceLimiter, error) | |||
|
|||
// Close cleans up open resources before the cloud provider is destroyed, i.e. go routines etc. | |||
Close() error |
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.
nit: In case there's no difference, could we rename this Close
to Cleanup
so that there are less func names to remember? 😉
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.
ok, will update this with the renamed interface method soon.
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.
@mmerrill3 Thanks for catching it!
I'd appreciate it if you could also rebase this onto the latest master so that hopefully @MaciekPytel can merge this earlier before this gets conflicted again 😃
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 am handling rebasing now.
if err := registry.regenerateCache(); err != nil { | ||
glog.Errorf("Error while regenerating Asg cache: %v", err) | ||
} | ||
}, time.Hour) |
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.
Ah, this does look bad. Thanks for the good catch!
One nit, but LGTM. Thank you very much for trying to fix the issue 👍 |
@mmerrill3 my attempt to resolve conflicts in github failed. Could you please do it yourself and push the new commit? |
And please squash the commits. |
c8d7ec9
to
eae3fdf
Compare
/lgtm |
Any chance to get this cherry picked into the next 1.0 patch release? Would this require a cherry pick PR? |
@johanneswuerbach - please create a cherry-pick |
Add shortnames to kueue APIs
Fix for issue 252 where excessive API calls to AWS are the result of leaking go routines from the Polling auto scaler.