-
Notifications
You must be signed in to change notification settings - Fork 4k
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
mig_info_provider.GetMigForInstance will now use locking when calli… #4660
mig_info_provider.GetMigForInstance will now use locking when calli… #4660
Conversation
/assign @MaciekPytel |
8d2ba8d
to
2145582
Compare
/assign @BigDarkClown |
@x13n: GitHub didn't allow me to assign the following users: BigDarkClown. Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@x13n: GitHub didn't allow me to request PR reviews from the following users: bpineau. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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 lock is miss-placed here, I think we should lock the GetXYZ
functions instead. Also checking the cache in fillMigInstances
introduced a bug, so we should not be doing that.
…ng the gce api. This is to avoid multiple gce calls for the same mig during scale down (which is done in parallel).
2145582
to
a906da2
Compare
After the changes this LGTM. @MaciekPytel, could you take a look and push approve button if everything is ok? |
/lgtm |
@BigDarkClown: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BigDarkClown, jayantjain93, towca The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
…ng the gce api.
This is to avoid multiple gce calls for the same mig during scale down (which is done in parallel).
Which component this PR applies to?
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: