Repository navigation
docs,op-acceptance-tests,op-devstack,op-service: cover an op-reth upgrade and rollback over a live datadir - #23427
Conversation
|
This pr has been automatically marked as stale and will be closed in 5 days if no updates |
c474193 to
35282e5
Compare
0e56ee4 to
82fc120
Compare
35282e5 to
2d72947
Compare
|
Claude: Detail moved out of the PR description when the branch was squashed into 82fc120. It is the description as it stood before the squash, unedited, so it describes the earlier commits. Every operator upgrades op-reth over a node's live datadir and proofs store, and rolls back when the upgrade misbehaves; nothing tested that path. The previous release is not built by this repo, so the package skips unless With previous = this branch's base (reth The devstack gains the seams the test needs (a per-node binary switch, a recorder of a node's process logs, a skip for binaries no package here builds) and a fix the test exposed:
Part of #23395. |
2d72947 to
a1ecc68
Compare
82fc120 to
09e9bee
Compare
a1ecc68 to
af31ccb
Compare
09e9bee to
44d938b
Compare
af31ccb to
8f5a66c
Compare
604eed8 to
fffdfb3
Compare
8f5a66c to
272c097
Compare
fffdfb3 to
faa379b
Compare
272c097 to
259913d
Compare
…rade and rollback over a live datadir Switch a node between the previous op-reth release and this tree's op-reth over its datadir and proofs store, after a clean stop or a SIGKILL, and require it to resume, keep up, serve historical proofs that match the sequencer's from the first pre-switch block on, and log no error, the replaced binary's shutdown included. The follower rollback cells are skipped naming ethereum-optimism/protocol-team#482: the previous op-reth aborts at startup decoding the ExEx WAL the reth 2.6 binary wrote. In the sequencer cells the batcher is stopped, so derivation cannot pull the sequencer back, and after a kill the follower is moved onto the rebuilt chain through the engine API before it must keep up over gossip. The devstack gains a binary switch that takes a path resolved before the chain starts and a recorder of a node's process logs. OpReth.Start fails as soon as the process exits, before or right after it announces its RPC servers, quoting its last unstructured stderr lines. logpipe.ParseRustStderr raises an unstructured stderr line to ERROR only when it looks like a Rust panic or abort, for op-reth, kona-node and op-zk-proposer. Part of #23395. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
259913d to
7f21b30
Compare
faa379b to
3b2c3bc
Compare
Operators upgrade op-reth over a live datadir and proofs store and roll back when the upgrade misbehaves; nothing tested that path.
op_reth_upgradeswitches a node between the previous release and this tree's op-reth over {follower, sequencer} x {clean stop, SIGKILL} x {upgrade, rollback} and requires it to resume, keep up and serve matching proofs. It skips unlessRUST_BINARY_PATH_OP_RETH_PREVIOUSis set; the follower rollback cells skip naming ethereum-optimism/protocol-team#482 (ExEx WAL decode).OpReth.Startnow fails as soon as the process exits.Stacked on #23421. Closes #23395. Local verification, findings and notes: detail comment.
Breakdown
AI Reviews
<ISODATETIME><COMMITID>Fable 5.1 xhigh<ISODATETIME><COMMITID>GPT-6.1-Sol xhigh<ISODATETIME><COMMITID>Opus 5.5 xhigh🤖 Generated with Claude Code