-
Notifications
You must be signed in to change notification settings - Fork 652
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
Concurrency issues with the EvictPod method #1388
Comments
I think that in a controller pattern, we should use locks to control concurrency. |
@googs1025 each plugin is run synchronously, along with each EvictPod request, so I don't think locks are necessary (unless you are referring to some sort of external lock implementation for running multiple descheduler instances?) Are you currently hitting any concurrency issues with descheduler? |
thank you for reply! |
Yes, this just calls the kubernetes API so we don't need to worry about concurrency there |
ok, I'll closed this issue. |
/close |
@googs1025: Closing this issue. 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. |
Does EvictPod need to be locked to control concurrency?
https://github.com/kubernetes-sigs/descheduler/blob/master/pkg/descheduler/evictions/evictions.go#L157
The text was updated successfully, but these errors were encountered: