-
Notifications
You must be signed in to change notification settings - Fork 29
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
Insertion failures cause segfault in concurrent index update actor #99
Comments
Some observations: it seems like to happen in the following scenario:
Now magically, I cannot reproduce it locally, but we do still see seg fault happening in our nightly correctness run: about a dozen out of 100K iterations. Thanks to the solid FDB KVS backing this, and due to the fact that the actual error(step |
The batch of inserts happening in a single request is run under a single transaction with the transaction loop present in
This issue deals with the second task. |
…r->onError() By not cleaning DocTransaction state which internally depends on FDB transaction state, concurrent actors during onError() are causing segfault.
A segmentation fault sometimes got thrown out from https://github.com/FoundationDB/fdb-document-layer/blob/master/src/QLContext.actor.cpp#L418
After some basic debugging it seems like somehow the memory of one of the item in Cartesian product iterator became invalid.
The text was updated successfully, but these errors were encountered: