-
Notifications
You must be signed in to change notification settings - Fork 782
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
validator client opens too many file descriptors #3468
Comments
We do close the keystore files after reading them, I think the issue you're encountering is due to the Increasing the file descriptor limit is the recommended workaround (as you know). Open to other ideas for addressing this as well though. |
my apologies, i didn't see these were the lock files, you are correct. i think this issue can only really manifest itself on testnets given how large of a stake you need, but it might be helpful to mention this in the docs in case someone else tries to run >1000 validators. |
What's the default limit for file locks? In my case that's unlimited while the file descriptors is 1024 as expected:
Could something like advisory locks work? I gave it a quick try using |
Completed in #4796 🎉 |
Description
when loading validator keys, lighthouse seems to keep file descriptors hanging, which leads to the validator failing to start when it's loading a lot of keys (2000 in my case)
Version
Lighthouse v2.5.1-df51a73
Present Behaviour
Expected Behaviour
the client should successfully start up with any number of validators and default linux config (ulimit of 1024).
Steps to resolve
close the file after reading a keystore
The text was updated successfully, but these errors were encountered: