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

Fill in additional versions when restoring storage state #3525

Closed
kostko opened this issue Nov 19, 2020 · 0 comments · Fixed by #3526
Closed

Fill in additional versions when restoring storage state #3525

kostko opened this issue Nov 19, 2020 · 0 comments · Fixed by #3526
Assignees
@kostko
Labels
c:bug Category: bug c:runtime Category: runtime c:storage Category: storage

Comments

@kostko
Copy link
Member

kostko commented Nov 19, 2020

When a runtime storage database from one network is used in a new network (e.g. when the consensus layer did a dump/restore upgrade) we should properly handle the case where there were additional rounds after the runtime has stopped (e.g., due to epoch transitions).

Currently the storage node doesn't know how to derive the missing roots so it is never synced.
@kostko kostko added c:storage Category: storage c:runtime Category: runtime c:bug Category: bug labels Nov 19, 2020
@kostko kostko self-assigned this Nov 19, 2020
@kostko kostko mentioned this issue Nov 19, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kostko kostko

Labels
c:bug Category: bug c:runtime Category: runtime c:storage Category: storage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

go/worker/storage: Fill in additional versions when restoring state oasisprotocol/oasis-core
1 participant
@kostko