Switch state-sync artifact level to operational #9388
Assignees
Labels
Comments
mhofman
changed the title
This was referenced May 20, 2024
mergify bot
added a commit
that referenced
this issue
Jun 3, 2024
closes: #9388 ## Description Switch from `replay` to `operational` for state-sync export/restore, genesis export/import, and as the default for cosmic-swingset's export/import of kernel DB command line tool. Drive by change of the default chain home directory for the import/export tool (this location was effectively changed a couple year ago but not consistently in the rest of the SDK). ### Security Considerations If all nodes prune historical "replay" artifacts, we lose the ability to perform replay based upgrades in the future. We expect archive nodes to not manually prune their DB in this way. ### Scaling Considerations This should have no impact on performance right now. In the future, when exporting the IAVL data is not as slow, this would reduce the time it takes for state-sync snapshots to be created. ### Documentation Considerations Should communicate this change with validators ### Testing Considerations Covered by existing integration tests. ### Upgrade Considerations Chain software change
mhofman
pushed a commit
that referenced
this issue
Jun 23, 2024
closes: #9388 ## Description Switch from `replay` to `operational` for state-sync export/restore, genesis export/import, and as the default for cosmic-swingset's export/import of kernel DB command line tool. Drive by change of the default chain home directory for the import/export tool (this location was effectively changed a couple year ago but not consistently in the rest of the SDK). ### Security Considerations If all nodes prune historical "replay" artifacts, we lose the ability to perform replay based upgrades in the future. We expect archive nodes to not manually prune their DB in this way. ### Scaling Considerations This should have no impact on performance right now. In the future, when exporting the IAVL data is not as slow, this would reduce the time it takes for state-sync snapshots to be created. ### Documentation Considerations Should communicate this change with validators ### Testing Considerations Covered by existing integration tests. ### Upgrade Considerations Chain software change
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
To support #9174, we need to stop requiring older transcript artifacts in state-sync snapshot. #9386 would cause most validators to no longer keep historical swing-store, which would cause a "replay" level snapshot to fail creation.
Description of the Design
In golang state-sync logic, change snapshot creation and restoration to use
operationallevel instead ofreplay.Security Considerations
None
Scaling Considerations
Smaller state-sync snapshots!
Test Plan
Manually?
Existing loadgen integration tests does exercise that state-sync works
Upgrade Considerations
Chain software upgrade.
The text was updated successfully, but these errors were encountered: