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

The status of state migration changed before the removal of old database #1412

Open
aidan-kwon opened this issue Jun 2, 2022 · 1 comment
Labels
issue/bug Issues with the code-level bugs.
Projects

Comments

@aidan-kwon
Copy link
Member

Problem
There is a problem if a node stops Klaytn process just after finishing state migration.
Because there are some steps after changing the status of state migration to finished, and removing old database especially takes some more time.

dbm.setStateTrieMigrationStatus(0)

If the node stops or kills Klaytn process just after finishing the state migration, the old database will not be removed. Even a user can encounter a more complicated situation that the migration is done but the new database isn't set to a main state trie database.

Mitigation
The status of state migration should be converted after removing the old database.

@exalate-issue-sync
Copy link

Exalate commented: Issue Created by: aidan-kwon

@sjnam sjnam added open/contribution welcome The fix or enhancement is approved and you are invited to contribute to it. issue/bug Issues with the code-level bugs. and removed Github open/contribution welcome The fix or enhancement is approved and you are invited to contribute to it. labels Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/bug Issues with the code-level bugs.
Projects
Misc
Awaiting triage
Development

No branches or pull requests

2 participants