sui_v1.84.1_1795145895_release: [1.84] Update tidehunter to 3ff977d (striped WAL relocation) (#28730)
- Version
sui_v1.84.1_1795145895_release- Repository
- MystenLabs/sui
Release notes
Description
The same change as #28729, for the 1.84 release branch, which also pins
tidehunter 5ec9021.
On testnet TideHunter fullnodes, the first relocation run that reaches
the restored snapshot copies the whole live object set before it frees
any WAL. On sui-node-mysten-rpc-th-0 that run took disk usage from 996
GB to 1,639 GB on a 1,584 GB volume.
This picks up tidehunter 3ff977d, one commit on top of the current pin
5ec9021. With it, WAL-based relocation works in stripes of 64 GiB.
After each stripe, it stores a control region and frees the WAL below
the stripe. A run then holds at most one stripe of copies above the
steady state. The expected peak is roughly +150–235 GB instead of +639
GB, and no per-node limit is needed. #28717 instead caps each run with
TH_RELOCATION_MAX_RECLAIM_PCT.
3ff977d is on the tidehunter striped-relocation branch and is not on
tidehunter main yet.
Test plan
This only changes the pinned commit. Tidehunter's manifests are
unchanged, so Cargo.lock needs only the new commit hash. Sui builds
the TideHunter Config with ..Config::default(), so the new
relocation_stripe_bytes setting takes its 64 GiB default. The
tidehunter commit adds tests showing that each stripe is freed before
the next one starts, and that a crash between stripes keeps the
completed stripes.
🤖 Generated with Claude Code
Release notes
Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.
For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.
• Protocol:
• Nodes (Validators and Full nodes):
• gRPC:
• JSON-RPC:
• GraphQL:
• CLI:
• Rust SDK:
• Indexing Framework: