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

Migration handlers for upgrading consensus state #2467

Closed
kostko opened this issue Dec 11, 2019 · 0 comments · Fixed by #2607
Closed

Migration handlers for upgrading consensus state #2467

kostko opened this issue Dec 11, 2019 · 0 comments · Fixed by #2607
Labels
c:common Category: common libraries

Comments

@kostko
Copy link
Member

kostko commented Dec 11, 2019

Depends on #2466.

As per #2446 we should support writing upgrade-specific migration handlers (based on the unique upgrade name specified in the upgrade descriptor). The upgrade handlers must run in the new binary before any consensus processing starts.

Ideally the old state should be backed up before the migration to support rollback in case of errors.
@kostko kostko added the c:common Category: common libraries label Dec 11, 2019
@kostko kostko mentioned this issue Dec 11, 2019
Closed
3 tasks
@jberci jberci mentioned this issue Feb 10, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c:common Category: common libraries
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade mechanism oasisprotocol/oasis-core
2 participants
@kostko @jberci