Skip to content
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

Closed
yaronyg opened this issue Dec 23, 2014 · 8 comments
Closed

Data corruption in LevelDB #3251

yaronyg opened this issue Dec 23, 2014 · 8 comments
Labels

Comments

@yaronyg
Copy link
Member

yaronyg commented Dec 23, 2014

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.

@nolanlawson
Copy link
Member

nolan@nolanlawson.com, I'll take a look

@daleharvey
Copy link
Member

Should be fixed in e38c6ef

@nolanlawson
Copy link
Member

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.

@nolanlawson nolanlawson reopened this Dec 27, 2014
@nolanlawson nolanlawson mentioned this issue Dec 27, 2014
@nolanlawson
Copy link
Member

@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. :)

@yaronyg
Copy link
Member Author

yaronyg commented Dec 28, 2014

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.

@daleharvey daleharvey removed the leveldb label Aug 4, 2015
@daleharvey
Copy link
Member

Closing as a dupe of #3251

@yaronyg
Copy link
Member Author

yaronyg commented Sep 8, 2015

@daleharvey you closed this bug as a dupe of itself. ?

@daleharvey
Copy link
Member

Sorry I meant #3216

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants