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

Filer: Too many open files after update to 2.38 #1980

Closed
divanikus opened this issue Apr 9, 2021 · 6 comments
Closed

Filer: Too many open files after update to 2.38 #1980

divanikus opened this issue Apr 9, 2021 · 6 comments

Comments

@divanikus
Copy link
Contributor

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.

tcp6   64937      0 192.168.65.42:8888      192.168.65.42:44366     ESTABLISHED 9150/weed
tcp6   45708      0 192.168.65.42:8888      192.168.65.42:41398     ESTABLISHED 9150/weed
tcp6   95248      0 192.168.65.42:8888      192.168.65.42:38762     ESTABLISHED 9150/weed
tcp6   50516      0 192.168.65.42:8888      192.168.65.42:36320     ESTABLISHED 9150/weed
tcp6    9399      0 192.168.65.42:8888      192.168.65.42:56408     ESTABLISHED 9150/weed
tcp6   63103      0 192.168.65.42:8888      192.168.65.42:38124     ESTABLISHED 9150/weed
tcp6    1927      0 192.168.65.42:8888      192.168.65.42:37842     ESTABLISHED 9150/weed
tcp6    6561      0 192.168.65.42:8888      192.168.65.42:41580     ESTABLISHED 9150/weed
tcp6   10021      0 192.168.65.42:8888      192.168.65.42:43408     ESTABLISHED 9150/weed
tcp6   22988      0 192.168.65.42:8888      192.168.65.42:58074     ESTABLISHED 9150/weed
tcp6   13524      0 192.168.65.42:8888      192.168.65.42:54530     ESTABLISHED 9150/weed
tcp6   50901      0 192.168.65.42:8888      192.168.65.42:47330     ESTABLISHED 9150/weed
tcp6   60016      0 192.168.65.42:8888      192.168.65.42:49604     ESTABLISHED 9150/weed
tcp6   53926      0 192.168.65.42:8888      192.168.65.42:44792     ESTABLISHED 9150/weed
tcp6   50842      0 192.168.65.42:8888      192.168.65.42:34476     ESTABLISHED 9150/weed
tcp6   32611      0 192.168.65.42:8888      192.168.65.42:39410     ESTABLISHED 9150/weed

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

  • List the command line to start "weed master", "weed volume", "weed filer", "weed s3", "weed mount":
weed filer -s3 -master=192.168.65.42:9333 -defaultReplicaPlacement=000 -s3.config=/etc/seaweedfs/config.json -s3.allowEmptyFolder -s3.port=9000
  • OS version: Debian 10.9
  • output of weed version: version 30GB 2.38 2327c07 linux amd64
  • if using filer, show the content of filer.toml:
[leveldb3]
# similar to leveldb2.
# each bucket has its own meta store.
enabled = true
dir = "/var/lib/weed/filer"                             # directory to store level db files
@chrislusf
Copy link
Collaborator

chrislusf commented Apr 9, 2021

If possible, can you send a "kill -3" to the weed filer process, and collect the screen output? This will kill the process, btw.

@divanikus
Copy link
Contributor Author

Sure. Here it is

@divanikus
Copy link
Contributor Author

I have reverted just filer to 2.35 and my cluster work A LOT faster.

@chrislusf
Copy link
Collaborator

Sure. Here it is

Is that all the output or is it truncated?

@divanikus
Copy link
Contributor Author

Oh, sorry, yes, it was truncated, because it 4MB long. Full one is here
out.zip

@chrislusf
Copy link
Collaborator

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants