fix(provider): cap storage_v2 unwind history by MDBX tip#23335
Merged
Conversation
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Contributor
|
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
joshieDo
commented
Apr 1, 2026
Comment on lines
+31
to
+36
| /// This is the committed txnid of the snapshot the reader is pinned to, not a unique per-reader | ||
| /// identifier, so multiple readers can report the same txnid. | ||
| /// | ||
| /// Used to check whether stale readers from a previous write transaction have completed. | ||
| /// Returns `None` if no readers are active or the backend does not support this query. | ||
| fn oldest_reader_txnid(&self) -> Option<u64> { |
Collaborator
Author
There was a problem hiding this comment.
this is especially important to understand
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
joshieDo
commented
Apr 1, 2026
Comment on lines
+215
to
+216
| /// Database handle used to inspect active MDBX readers during unwind commits. | ||
| reader_txn_tracker: Option<Arc<dyn ReaderTxnTracker>>, |
Collaborator
Author
There was a problem hiding this comment.
this is essentially Database/DatabaseEnv, but didn't want to make it such an hard dependency. wdyt
Member
There was a problem hiding this comment.
yeah having this generic over DB would be a mess
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
klkvr
reviewed
Apr 1, 2026
Comment on lines
+215
to
+216
| /// Database handle used to inspect active MDBX readers during unwind commits. | ||
| reader_txn_tracker: Option<Arc<dyn ReaderTxnTracker>>, |
Member
There was a problem hiding this comment.
yeah having this generic over DB would be a mess
Comment on lines
+1552
to
1557
|
|
||
| // Only the prefix up to `visible_tip` should influence routing for this reader. Any | ||
| // later Rocks history entries are not yet visible in the companion MDBX snapshot. | ||
| let visible_count = chunk.rank(visible_tip); | ||
| let (rank, found_block) = compute_history_rank(&chunk, block_number); | ||
|
|
Member
There was a problem hiding this comment.
hmm couldn't we simplify this by assuming that visible_tip > block_number?
i was thinking that given that this always holds we basically have 2 cases
found_block > visible_tipwhich means that rocksdb is ahead AND we can safely treat this asfound_block = Nonebecause the earliest block the key was changed in is after our mdbx viewfound_block <= visible_tipwhich can be handled as is
Amp-Thread-ID: https://ampcode.com/threads/T-019d4937-7f0e-765b-bf61-489758cb324c Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019d4435-3bfe-7739-b47f-fbcf6473a16a Co-authored-by: Amp <amp@ampcode.com>
klkvr
approved these changes
Apr 2, 2026
github-merge-queue Bot
pushed a commit
to tempoxyz/tempo
that referenced
this pull request
Apr 3, 2026
Automated nightly update of reth dependencies from `paradigmxyz/reth` main branch. ## Upstream reth changes [`f8efc76...c82d435`](paradigmxyz/reth@f8efc76...c82d435) 🔗 Amp thread: https://ampcode.com/threads/T-019d517e-981b-75fd-b3cf-8ad2455f38f6 **RPC** - Remove `0x` prefix from `admin_peers` id and return keccak256 node ID in `admin_nodeInfo.id` to match go-ethereum format ([#23318](paradigmxyz/reth#23318), [#23319](paradigmxyz/reth#23319)) - Apply count filter only after `after` is consumed in pagination ([#23338](paradigmxyz/reth#23338)) - Pre-allocate vectors in `eth_feeHistory` ([#23334](paradigmxyz/reth#23334)) - Add `bal` RPC methods ([#23330](paradigmxyz/reth#23330)) **Engine** - Include backpressure in reported `persistence_wait`, make wait-time mimic CL slot time ([#23308](paradigmxyz/reth#23308)) **Perf** - Reduce cacheline ping-pong in workers availability ([#23321](paradigmxyz/reth#23321)) **Net** - Avoid itertools `Format` panic in tracing log ([#23331](paradigmxyz/reth#23331)) **DB** - Cap `storage_v2` unwind history by MDBX tip ([#23335](paradigmxyz/reth#23335)) **Bench** - Add warmup step for big blocks mode ([#23323](paradigmxyz/reth#23323)) - Make payload handling ethereum-only ([#23324](paradigmxyz/reth#23324)) - Use repository instead of GitHub Actions cache to track hourly runs ([#23306](paradigmxyz/reth#23306)) - Upload nightly regression results to ClickHouse ([#23344](paradigmxyz/reth#23344)) **Chore** - Migrate `allow(clippy::` to `expect(clippy::` ([#23340](paradigmxyz/reth#23340)) - Remove unused return value from `dispatch_with_chunking` ([#23341](paradigmxyz/reth#23341)) - Update nixpkgs to 25.11 and refresh flake inputs ([#23342](paradigmxyz/reth#23342)) ## Migrations 🔗 Amp thread: https://ampcode.com/threads/T-019d517e-baf0-727b-a57e-0488240af973 - **Reth dependency bump**: All `reth-*` git dependencies updated from rev `f8efc76` to `c82d435` - **New `GetBlockAccessList` trait impl**: `TempoEthApi` now implements `GetBlockAccessList` (imported from `reth_rpc_eth_api::helpers::bal`), likely a new required trait added upstream in the reth update [GitHub Workflow](https://github.com/tempoxyz/tempo/actions/runs/23933027282) --------- Co-authored-by: Arsenii Kulikov <klkvrr@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Alternative to #23291 and #23305.
For
storage_v2unwind, this keeps the MDBX-first ordering but waits after the MDBX commit and beforeRocksDBso a reader opened before the unwind cannot observe unwound MDBX state and then later route through pre-unwind Rocks history.It then caps
RocksDBhistory lookups by the reader's MDBX-visible tip instead of adding a second wait/fence. Example: if a reader's MDBX snapshot only sees blockN, a later Rocks snapshot ignores history entries aboveNand falls back to the MDBX-visible prefix instead of routing into a newer changeset.Also drops the validation RO provider before
unwind_provider_rw()so the unwind wait cannot block on that provider itself.