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

Failed transaction, executes after reopening Env. But won't execute on newely created Env #71

Closed
kk00ss opened this issue Jun 27, 2016 · 1 comment

Comments

@kk00ss
Copy link

kk00ss commented Jun 27, 2016

Reopening same environment, and performing just about the same transaction is totally fine. But when I create env, or copy env which was created, but never written to - transaction fails. Most likely an issue with LMDB, but since people using this project might have seen something like that - I'm asking it here.
code for reproducing - there is quite a lot going on in Repository class. Just attempting to save 39KB results in an error, so I commented the line this.documentDB.put(tx, key.adday(), doc._2)

Any clues would be appreciated.
UPD: Now I see #70 . Probably there is nothing more specific on this behavior.

@kk00ss kk00ss changed the title MDB_BAD_TXN on newely created environment. Failed transaction, executes after reopening Env. But won't execute on newely created Env Jun 27, 2016
@kk00ss
Copy link
Author

kk00ss commented Jun 27, 2016

It's strange but environment is changed after failed transaction, only headers. They probably contain the answer of why it works after restart. Hex compare of mdb files. I guess nothing else is changed - so I'm closing the issue..

@kk00ss kk00ss closed this as completed Jun 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant