-
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
some problems with 5.6.1 #2733
Comments
|
Hi @framlog. The latest release is 5.7.1. All the versions we tagged on https://github.com/facebook/rocksdb/releases are considered stable at the time we release, though there can be issues found later on, and we bump minor version with hot fixes. Regarding pipelined write, are you seeing the threads get deadlock at waiting the condition variable, or are they able to advance? If it is not deadlock, what you see is expected. Our current implementation for write is that one thread will be the leader doing the actual write for other concurrent writers (the followers), and followers wait on the condition variable until the leader finishes. We'll add more documents to describe the behavior later. Regarding issue with Get(), can you try compile with ASAN and provide the error logs printed by ASAN? |
Thanks for reply. Well, for the first problem, threads stalled at waiting the condition variable, but I don't sure about it's a bug of rocksdb after a review today since the server may restart while having a plethora of wallog. Also, I've read the logic of the write procedure but didn't think it had some bugs in it. |
Asan didn't generate any useful information, it just repeated the core stack. Is it because I didn't enable asan properly(I compiled the library with |
I fixed this problem by changing |
Hi,
What's the version of the stable release package?
I upgraded the rocksdb version from 4.6 to 5.6.1 recently, but it seems to have many problems. For example, we encounter a write stall after tcpcopy running a while with the pipeline write enabled (specifically, 9 of 10 write threads stall at waiting the condition variable, and only one thread can work normally.) Or I even got a core dump at
Get
method(it seems that I got a use after free...).I have to say we modified some code of it a bit but these problems happened without enabling the customized logic.
Besides, I get confused after seeing the version of release packages and its corresponding dates.
The text was updated successfully, but these errors were encountered: