-
Notifications
You must be signed in to change notification settings - Fork 40k
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
queueActionLocked requires write lock #30839
Conversation
LGTM. Thanks. cc @wojtek-t. |
GCE e2e build/test passed for commit 3e69c5a. |
Bump to P2 as it's potentially fixing the scalability tests. |
Thanks (though I'm not 100% sure it will fix the problem). |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 3e69c5a. |
Automatic merge from submit-queue |
@wojtek-t my theory is that it's a false positive-- that something in the Pop() routine (which was on the stack) just finished a read and now there's a write. Actually this theory may or may not make sense depending on how the map is determining that it's being concurrently accessed. Having Resync called concurrently could cause it too, but there wasn't evidence of that. |
@deads2k ^ see last comment. |
Some slowness seems to have been introduced starting / stopping pods when this PR applied. |
Hm. This would block lists and gets, where it formerly wouldn't (and now that I look at it, there was a genuine problem where list reads the things that Resync writes). I can make a change to unlock periodically, not sure if it will help. @wojtek-t @gmarek fyi in case this shows up in scalability tests. |
@andrewgdavis would you like to try #30948 in your setup and see if it makes things better or worse? |
Not sure if this should be part of this PR or if a new one should be opened and reference this. Any way, with this PR the following occured: (note the follow-up which is 30948 has not yet been applied.)
|
Automatic merge from submit-queue Do not hold the lock for a long time Followup to #30839. I'm not convinced this is a super great idea but I'll throw it out and let others decide. Ref kubernetes/minikube#368 Ref #30759
Fix kubernetes/minikube#368
Fix part of #30759
Hopefully. On stack dumps I couldn't see who was fighting with this.
This change is