You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As part of support for chain upgrades (#1804), we've started hosting minimal archives of post-migration state for late-joining nodes, e.g. #4520. Those archives include the post-migration genesis-file, a priv-validator-state json config with the upgrade height set as the minimum, and the historical rocksdb data.
Describe the solution you'd like
We should also include cometbft data in the historical archives. Doing so would allow reindexing of historical events into a sidecar database.
Describe alternatives you've considered
We could not do this. But we need to do it anyway for the services like the block explorer on the testnet, so we might as well document the procedure and support it.
Additional context
We have historical backups of pre-upgrade state that can be used to build the archives. During discussions with @erwanor, he pointed out that we want at least the cometbft data dir, plus config.toml and genesis. We should probably also recommmend running with flags like --p2p.pex=false and --p2p.seeds=''.
The text was updated successfully, but these errors were encountered:
## Describe your changes
Refs #4582
Also relevant is #4525 which the archive referenced in this PR does
_not_ account for; 4524 is still outstanding.
To test this, one should be able to join the post-upgrade Testnet 78
with v0.78.0 of pd and sync blocks.
## Issue ticket number and link
## Checklist before requesting a review
- [x] If this code contains consensus-breaking changes, I have added the
"consensus-breaking" label. Otherwise, I declare my belief that there
are not consensus-breaking changes, for the following reason:
> docs-only
Co-authored-by: Conor Schaefer <[email protected]>
Is your feature request related to a problem? Please describe.
As part of support for chain upgrades (#1804), we've started hosting minimal archives of post-migration state for late-joining nodes, e.g. #4520. Those archives include the post-migration genesis-file, a priv-validator-state json config with the upgrade height set as the minimum, and the historical rocksdb data.
Describe the solution you'd like
We should also include cometbft data in the historical archives. Doing so would allow reindexing of historical events into a sidecar database.
Describe alternatives you've considered
We could not do this. But we need to do it anyway for the services like the block explorer on the testnet, so we might as well document the procedure and support it.
Additional context
We have historical backups of pre-upgrade state that can be used to build the archives. During discussions with @erwanor, he pointed out that we want at least the cometbft data dir, plus config.toml and genesis. We should probably also recommmend running with flags like
--p2p.pex=false
and--p2p.seeds=''
.The text was updated successfully, but these errors were encountered: