-
Notifications
You must be signed in to change notification settings - Fork 240
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
versiondb lastest version don't match iavl latest version #1301
Comments
yes, this is known issue with ungraceful shutdown, for now there are some tricks you can do to recover fast, for example for rocksdb:
|
yihuang
added a commit
to yihuang/cronos
that referenced
this issue
Jan 26, 2024
Closes: crypto-org-chain#1301 Solution: - do fsync when writing versiondb
13 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 29, 2024
* Problem: versiondb lag behind when os reboot Closes: #1301 Solution: - do fsync when writing versiondb * Update CHANGELOG.md Signed-off-by: yihuang <huang@crypto.com> * relax version checking * changelog --------- Signed-off-by: yihuang <huang@crypto.com>
mmsqe
pushed a commit
to mmsqe/cronos
that referenced
this issue
Jan 30, 2024
* Problem: versiondb lag behind when os reboot Closes: crypto-org-chain#1301 Solution: - do fsync when writing versiondb * Update CHANGELOG.md Signed-off-by: yihuang <huang@crypto.com> * relax version checking * changelog --------- Signed-off-by: yihuang <huang@crypto.com>
mmsqe
pushed a commit
to mmsqe/cronos
that referenced
this issue
Jan 30, 2024
* Problem: versiondb lag behind when os reboot Closes: crypto-org-chain#1301 Solution: - do fsync when writing versiondb * Update CHANGELOG.md Signed-off-by: yihuang <huang@crypto.com> * relax version checking * changelog --------- Signed-off-by: yihuang <huang@crypto.com>
mmsqe
added a commit
that referenced
this issue
Jan 30, 2024
…1306) * Problem: memiavl rootmulti store access map concurrently (#1302) * Problem: memiavl rootmulti store access map concurrently Solution: - code refactoring * Update CHANGELOG.md Signed-off-by: yihuang <huang@crypto.com> --------- Signed-off-by: yihuang <huang@crypto.com> * mod tidy * Problem: versiondb lag behind when os reboot (#1304) * Problem: versiondb lag behind when os reboot Closes: #1301 Solution: - do fsync when writing versiondb * Update CHANGELOG.md Signed-off-by: yihuang <huang@crypto.com> * relax version checking * changelog --------- Signed-off-by: yihuang <huang@crypto.com> * fix lint --------- Signed-off-by: yihuang <huang@crypto.com> Co-authored-by: yihuang <huang@crypto.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
recently I reboot our server, then cronosd reports the following error on starting:
"versiondb lastest version 12063409 don't match iavl latest version 12063413"
I guess maybe cronosd doesn't stop gracefully when I reboot the server, maybe I should terminate cronosd before reboot the server. This is not 100% reproducible, a normal restart of the cronosd doesn't got this issue.
While despite that, could we have a self-healing approach to auto fix the mismatched version instead of failed to start, like rollback iavl version to match versiondb?
cronosd version: v1.0.14
The text was updated successfully, but these errors were encountered: