This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
media repo worker leaks open FDs #9488
Comments
This looks to me like |
I'd be curious if we're seeing this on a server that is not using the S3 provider, just to narrow down the potential cause. There was also a useful comment from the previous issue: #8653 (comment)
|
clokep
added
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
labels
Feb 24, 2021
This comment has been minimized.
This comment has been minimized.
given the destinations in question for those CLOSE_WAIT sockets, I'd be surprised if S3 was relevant here. |
This comment has been minimized.
This comment has been minimized.
Unfortunately it seems like #9497 did not fix this. 😢 I'll need to keep investigating. |
I was unable to reproduce this, so this needs a bit more investigation. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There is a sawtooth on the "Open FDs" graph for the media repository: they accumulate until a Gen 2 GC happens:
The accumulated FDs appear to be
CLOSE_WAIT
sockets; they mostly appear to be outbound connections to port 80 or 443 so they are probably related to url preview requests.The text was updated successfully, but these errors were encountered: