From 97538e1f0796b82b05cc69275e1df4610bdb5734 Mon Sep 17 00:00:00 2001 From: David Snelling Date: Mon, 17 Aug 2026 14:44:59 -0700 Subject: [PATCH] =?UTF-8?q?docs(releases):=20the=2010.2.0=20consumer=20ent?= =?UTF-8?q?ry=20=E2=80=94=20adoption=20completes=20in=20one=20call?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- RELEASES.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/RELEASES.md b/RELEASES.md index 8116db0e..602b84e4 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -31,6 +31,30 @@ is sometimes cited as a 7.x removal — those methods never existed on 7.x; the --- +## v10.2.0 — 2026-08-17 (adoption completes in one call) + +One fix, headline-sized for large stores. Pairs with the same native accelerator +version as 10.1.0 — no accelerator bump needed. + +- **The adoption backfill runs to completion.** Adopting the crash-safe storage + authority first re-commits every row the log never saw (a one-time baseline + backfill). That backfill had a fixed ceiling of 800 rows per + `adoptLogAuthority()` call — sized for small drift, not for a large pre-existing + store — so a store with a 12,700-row baseline advanced 800 rows per call and + stayed on the prior authority across restarts (a production deployment's + report). Now one call adopts a baseline of any size: the backfill sees the + entire curable set at once, cures all of it, and loops only until green — the + no-progress guard is the sole stop. Pace rides the write path (~100 rows/s + measured end to end, versus ~1.7 rows/s under the old page-per-scan shape), + and progress is narrated so an operator watching a live service sees motion. + Stores that already adopted are unaffected; stores still on the prior authority + flip in a single call on their next open or on an explicit + `adoptLogAuthority()`. +- Verification report unchanged on the wire (still lists at most 200 mismatches; + counts remain complete) — only the adoption path reads the full set. + +--- + ## v10.1.0 — 2026-08-13 (the bounded-recovery and write-path-cure release) The theme: **crash recovery is bounded, restores are durably founded, and two