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.

Sign up for GitHub

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

Jump to bottom

Upgrade from 3.2 to 3.2.1 reset autoincrement keys #3059

Closed
DeShadow opened this issue Aug 17, 2017 · 5 comments
Closed

Upgrade from 3.2 to 3.2.1 reset autoincrement keys #3059

DeShadow opened this issue Aug 17, 2017 · 5 comments
Labels
1 Bug 2 Fixed Resolution 3 Core
Milestone
3.2.2

Comments

@DeShadow
Copy link

I upgraded my Arango database from 3.2 to 3.2.1
And my autoincrement keys were reseted. That's why after founding of problem I had to dump-restore all my data again.
@jsteemann
Copy link
Contributor

Are you using MMFiles or RocksDB storage engine?

@DeShadow
Copy link
Author

@jsteemann RocksDB

dhly-etc pushed a commit that referenced this issue Aug 17, 2017
Fixed issue with autoincrement data not being persisted properly in R…
3f843be 
…ocksDB (#3059).
fceller pushed a commit that referenced this issue Aug 17, 2017
@fceller
Fixed issue with autoincrement data not being persisted properly in R…
2294fbc 
…ocksDB (#3059). (#3067)
ObiWahn added a commit that referenced this issue Aug 18, 2017
@ObiWahn
Merge branch 'devel' of https://github.com/arangodb/arangodb into fea…
4002a0a 
…ture/planning-499-different-error-codes-for-version-check

* 'devel' of https://github.com/arangodb/arangodb:
  Feature/remove manual zippery (#3036)
  Fixed issue with autoincrement data not being persisted properly in RocksDB (#3059). (#3067)
  Bug fix/issues 1708 (#3060)
  Fix issue #3037: Foxx, internal server error when I try to add a new service (#3056)
  Bug fix/v8 syslog (#3055)
  Bug fix/small issues 1608 (#3049)
  fixed issue #3044 (#3048)
  fixed issue #3039 (#3045)
  Fix foxx github url (#3042)
  we need to substitute the package name here too - else enterprise pac… (#3025)
  Fixing engine stats in arangosh (#3038)
  MSVC is pendantic (but right) (#3047)
  reduce log spam (#3051)
  Feature/build docker to build using stretch container (#3062)
  build docker to build using stretch container (#3061)
  fix and extend journal-related tests (#3043)
@dhly-etc dhly-etc added this to the 3.2.2 milestone Aug 18, 2017
@dhly-etc
Copy link
Contributor

The bug is actually not related to upgrade, per se, but results from a missing call in our recovery code. In circumstances where there are no document writes remaining in the WAL for a collection with autoincrement keys, the recovery code would not update the key generator's last-issued value. This has since been fixed and will be in the 3.2.2 release.

@DeShadow
Copy link
Author

@danielhlarkin Thanks, Dan! :)

@dothebart
Copy link
Contributor

ArangoDB 3.2.2 containing this bugfix is available for download - thanks for reporting.

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 Bug 2 Fixed Resolution 3 Core
Projects
None yet
Milestone
3.2.2
Development

No branches or pull requests
4 participants
@jsteemann @DeShadow @dothebart @dhly-etc