-
Notifications
You must be signed in to change notification settings - Fork 122
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
segmentation fault : rocksdb : Too many open files #3098
Comments
it seems btw to work with https://defi-snapshots-europe.s3.eu-central-1.amazonaws.com/snapshot-mainnet-4268284.zip
but this seems not to be the problem, cause the fd count already drops to around 1600 before the error occurs
script to measure open file descriptors
|
Related: facebook/rocksdb#10367 |
Thanks for the detailed info @skutcher. We're looking at options to workaround this. For now, please push the kernel limits and ulimits to higher. We've observed anything 16k+ usually works well. We'll look at a more refined fix soon. |
yfyi: my default system limit:
but as mentioned above if i increase the softlimit i got just buffer overflows |
I assume this after it already failed and corrupted the data due to open files? Once the data is corrupt, all bets are off I'm afraid. Even if it doesn't error with something else, the integrity checks will fail to ensure the node doesn't start with bad data. This is expected behavior. If you have issues with a clean data / snapshot, please let us know. We do run our machines with 1024 * 1024 or 16k as the file open limits depending on the system. We do intend to workaround the rocksdb bug, but however, meanwhile the above should be a viable workaround. I've also expanded a bit more on #3101 (comment) |
I am pretty sure it was with an fresh snapshot of https://defi-snapshots-europe.s3.eu-central-1.amazonaws.com/snapshot-mainnet-4423468.zip . I will check again to be 100% sure |
We were able to test with stricts ulimit < 1024, and now the default should work well with the default of 1024 even though it's recommended to have higher limits. Believe this issue should be resolved with the latest master. |
Closing, as this is now resolved. Please feel free to reopen if you continue to have issues with >= 4.2.1. |
Summary
Steps to Reproduce
Environment
RUST_BACKTRACE=full
The text was updated successfully, but these errors were encountered: