pd: add support for running in paused 'archive node' mode #4494
Assignees
Labels
A-upgrades
Area: Relates to chain upgrades
needs-refinement
unclear, incomplete, or stub issue that needs work
Comments
github-actions
bot
added
the
needs-refinement
29 tasks
|
In support of the upcoming #4497, want a much slimmer implementation:
We already have migration code that does this: https://github.com/penumbra-zone/penumbra/blob/319a3d925e201be3d061536fc68951df714e1860/crates/bin/pd/src/migrate/reset_halt_bit.rs, it just needs to be wired up to the CLI. |
conorsch
added a commit
that referenced
this issue
May 29, 2024
Adds a new flag to `pd migrate --ready-to-start` that makes an in-place edit to local state, setting an enabled halt bit to false. Refs #4494.
1 task
conorsch
added a commit
that referenced
this issue
May 30, 2024
Adds a new flag to `pd migrate --ready-to-start` that makes an in-place edit to local state, setting an enabled halt bit to false. Refs #4494.
|
Now that we have #4499, I think we can deprioritize this work to post-v1. Separately I'm working on reindexing an event db from historical backups. As long as that works end-to-end, I believe we can get by with the functionality we have today. |
conorsch
added a commit
that referenced
this issue
Jun 12, 2024
Collects some information from the cuiloa README [0], as well as some generalized instructions captured in #4566, particularly the use of `--ready-to-start` from #4499. Refs #4494, closes #4566. [0] https://github.com/penumbra-zone/cuiloa/blob/dc4133f7b36706cdf5a3ee6b4e0fb2c09e5a8bb8/README.md
conorsch
added a commit
that referenced
this issue
Jun 13, 2024
Collects some information from the cuiloa README [0], as well as some generalized instructions captured in #4566, particularly the use of `--ready-to-start` from #4499. Refs #4494, closes #4566. [0] https://github.com/penumbra-zone/cuiloa/blob/dc4133f7b36706cdf5a3ee6b4e0fb2c09e5a8bb8/README.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
In the CometBFT ecosystem, an 'archive node' refers to a node that is running an from an old (pre-upgrade) genesis, used to serve Comet RPC requests for data during that epoch. Post upgrade, any state from a pre-upgrade epoch is not queryable by the CometBFT RPC. This presents a problem for use cases such as relayers, which use the Comet RPC in order to fetch headers to use to build client updates. As such, it is typical for CometBFT operators to run a pre-upgrade node in a 'frozen' state, where that node only exists to serve RPC requests for headers from the pre-upgrade epoch, known as an 'archive node'.
There is not currently a natively supported pathway in
pdfor running in 'archive' mode (not producing any blocks, but still remaining online so as not to halt CometBFT).Describe the solution you'd like
We should add a flag to
pd start,pd start --archive, that configurespdso that it expects to run in a frozen 'archive' state.--archiveshould:pdto not respond to any consensus-related ABCI requests. This should be done in a way that avoidspdor CometBFT halting.pdto not respond to any mempool-related ABCI requests. This should be done in a way that avoidspdor CometBFT halting.The text was updated successfully, but these errors were encountered: