docs: ibc relaying and chain upgrades #25
Conversation
pages/node/pd/indexing-events.md
Outdated
| @@ -28,7 +28,7 @@ planned upgrade. The process then becomes: | |||
| 1. Restore node state from backup. | |||
| 2. Ensure you're using the appropriate `pd` and `cometbft` versions for the associated state. | |||
| 3. Run `pd migrate --ready-to-start` to permit `pd` to start up. | |||
| 4. Run CometBFT with extra options: `--p2p.pex=false --p2p.seeds='' --moniker archive-node-1` | |||
| 4. Run CometBFT with extra options: `--p2p.pex=false --p2p.seeds='' --p2p.persistent_peers='' --p2p.laddr="tcp://127.0.0.1:26656" --moniker archive-node-1` | |||
There was a problem hiding this comment.
These options are based on feedback we received from TM/CMT folks on best practices. Trying to be specific, but there's actually a lot one needs to do to make sure a node is not talking to peers, like nuking the address book. Even if the node does peer and disagrees about block contents, it'll still serve its RPC, which means its still suitable for as an archive node, at least for relaying.
There was a problem hiding this comment.
Added a step to move aside the addrbook, after conferring with some relayer operators about best practices.
|
Visit the preview URL for this PR (updated for commit aea20cb): https://penumbra-guide--pr25-relayer-upgrades-68xtp1ht.web.app (expires Wed, 14 Aug 2024 21:54:10 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: c64218fe717b75c9724a23946df883a1adf10faa |
Add more detailed descriptions of running an archive node and performing genesis-restart maintenance for relayers.
conorsch
force-pushed
the
relayer-upgrades
branch
from
9f83951
to
aea20cb
Compare
|
Updated based on recent feedback. Ready for review! |
First pass at making sure the necessary steps for updating relayers across upgrade boundaries are well documented.