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
Data corruption in LevelDB #3251
Comments
nolan@nolanlawson.com, I'll take a look |
Should be fixed in e38c6ef |
I think this is actually still an issue, because @yaronyg found a case where doc A's seq pointed to the seq of doc B. Even without the readqueue/writequeue in place, that shouldn't happen. I'd like to investigate a bit more before closing. |
@yaronyg I've been trying to reproduce what happened to your database and cannot. I think the first step will be a reproducable test. Else try your steps again with pouchdb master and see if it magically fixes it somehow. :) |
The failure was always intermittent so I don't have an immediate repro. This is why I wanted the chaos monkey tests to give us some hope of testing or atomicity and consistency. |
Closing as a dupe of #3251 |
@daleharvey you closed this bug as a dupe of itself. ? |
Sorry I meant #3216 |
I'm running in node.js. The program I wrote did a bunch of PUT requests. I then did a GET request and got a "wrong doc returned' error here. The stack points to here.
If anyone is going to work on this bug then just send me your email address and I'll mail you a link to the corrupt DB file.
The text was updated successfully, but these errors were encountered: