-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
UPSTREAM: 36248: Fix possible race in operationNotSupportedCache #11791
Conversation
Because we can run multiple workers to delete namespaces simultaneously, the operationNotSupportedCache needs to be guarded with a mutex to avoid concurrent map read/write errors.
[test] |
LGTM |
#11452 [test] |
Evaluated for origin test up to 0b30b0d |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11155/) (Base Commit: da2c207) |
[merge] |
[merge] On Saturday, November 5, 2016, OpenShift Bot notifications@github.com
|
[merge] On Saturday, November 5, 2016, OpenShift Bot notifications@github.com
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11155/) (Image: devenv-rhel7_5328) |
#11452 [merge] |
Evaluated for origin merge up to 0b30b0d |
Because we can run multiple workers to delete namespaces simultaneously, the
operationNotSupportedCache needs to be guarded with a mutex to avoid concurrent
map read/write errors.
@liggitt
Fixes #11584