-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Filer: Too many open files after update to 2.38 #1980
Comments
If possible, can you send a "kill -3" to the |
Sure. Here it is |
I have reverted just filer to 2.35 and my cluster work A LOT faster. |
Is that all the output or is it truncated? |
Oh, sorry, yes, it was truncated, because it 4MB long. Full one is here |
thanks! added a fix. |
mirdhyn
pushed a commit
to ueni-ltd/seaweedfs
that referenced
this issue
May 3, 2021
fix seaweedfs#1980 reverting the file upload batch executor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After upgrading from 2.35 to 2.38 we experience full service degradation after several hours of work. I see lots of ESTABLISHED connections to filer and "too many open files" errors in filer's log.
LimitNOFILE is set to 65535. I'm seeing literally thousands of open and non-closing sockets. I'm using filer as s3 gateway.
System Setup
weed version
: version 30GB 2.38 2327c07 linux amd64filer.toml
:The text was updated successfully, but these errors were encountered: