-
Notifications
You must be signed in to change notification settings - Fork 41.6k
Graceful shutdown fsnotify watcher #135078
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
base: master
Are you sure you want to change the base?
Conversation
|
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Jefftree The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
I prefer to add a ctx parameter to the existing Run() function in the FSWatcher interface. It seems many files need to be changed to pass the ctx parameter to the Run() function. But it can avoid forgetting to call the Close() function. i.e., https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-proxy/app/options.go#L290-L391 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
The fsnotify watcher has a
Run()function that fetches indefinitely with no way to stop, resulting in a goroutine leak:https://github.com/kubernetes/kubernetes/blob/master/pkg/util/filesystem/watcher.go#L77-L93
Which issue(s) this PR is related to:
Fixes #135076
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig storage