-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Core dump when opening a new rocksdb database #4900
Comments
I am afraid there is not much I can tell from the stack trace. If you build a debug version of RocksJava and then run that, any line numbers will then be resolvable with addr2line - https://github.com/facebook/rocksdb/wiki/JNI-Debugging |
Thanks @adamretter for your reply. |
@adamretter When I copied the generated rocksdb java jar: rocksdbjni-5.14.2-linux64.jar into my war, it cored dump during start with the following stack:
The code at cache/lru_cache.cc:475:
Not sure why the debug version would fail at that point. Thanks a lot. |
You likely want:
|
@adamretter Thanks for your help. |
We are using org.rocksdb:rocksdbjni:5.14.2, and the core dump happened when opening a new rocksdb database and it doesn't happen consistently.
When this issue happened, there were several RocksDB open/close/data read operations.
Here is the stack generated by Java, and we haven't got core dump file yet since it is not easy to reproduce:
When I tried to use
addr2line
to get the line number, and it didn't print any useful info so it might be the lib we are using didn't compile with '-g' operation.addr2line -e librocksdbjni7645520449361009434.so 0x383ca6
??:0
Have you guys seen this issue before?
On our end, we will try to reproduce it and get the core dump file later.
Expected behavior
Actual behavior
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: