Skip to content
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

BUG: possible TCP connection/file descriptor leak by calling HTTP probes #143

Closed
dinoallo opened this issue Feb 3, 2024 · 1 comment
Closed

Comments

@dinoallo
Copy link

dinoallo commented Feb 3, 2024

Version

Description

Currently, doing an HTTP probe requiring allocating a new http.Client and http.Transport, and the underlying connections managed by http.Transport might be ESTABLISHED indefinitely if no parties (client or server) directly close them. As a result, if the probes continuously happen, we can see TCP connections opened by one process
(e.g. image-cri-shim) drastically increase.

How to reproduce the bug?

  1. Deploy image-cri-shim
  2. Deploy several containers with invalid image names and wait for a couple of hours
  3. Check the host node of the containers
  4. Use ss or netstat to inspect connection
@dinoallo
Copy link
Author

dinoallo commented Feb 3, 2024

Directly close idle connections like this commit: 0e6deb6 can fix this issue.

cuisongliu added a commit to labring/operator-sdk that referenced this issue Apr 15, 2024
cuisongliu added a commit to labring/operator-sdk that referenced this issue Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant