Complete M7.9b upgrade barrier and durability qualification

Schema v8 binds authority to builds (ADR-0068): acquisition names the
host build and only retained, unretired builds may hold a lease; no
commit may name a retired build; upgrade_barrier retires a build and
fences every holder in one transaction, while build-less pre-v8 hosts
keep working until the first barrier. Tests cover a writer surviving a
failed and then a real online migration, old-writer fencing on every
path, whole-history recovery by the new build, and the M7 qualification
fixture (19.6 s SIGKILL-to-ready under the production lease, no lost
acknowledgements).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-29 07:31:04 -04:00
co-authored by Claude Opus 5.5
parent 703f67834f
commit f59cca2c3b
24 changed files with 893 additions and 52 deletions
+26
View File
@@ -928,3 +928,29 @@ configurations; the PostgreSQL suites passed in three.
Next: M7.9b, covering the upgrade barrier and old-writer fencing, schema
migration failure while a host is serving, and measured recovery and batching
latency.
## M7.9b upgrade barrier and durability qualification (2026-09-29)
ADR-0068 and schema v8 bind authority to builds:
- Acquisition names the host's build, and only a retained build that has not been
retired may hold a lease.
- No commit may name a retired build.
- `upgrade_barrier` retires a build and fences every holder in one transaction.
- Hosts built before M7.9b keep working until the first barrier.
A lease-holding writer survived a failed v8 migration (the database stayed at v7
exactly) and then the real migration. After the barrier it could never regain
authority. The new build recovered the whole history, including links written by
the retired build.
Qualification (engineering/DURABILITY_QUALIFICATION.md), under the production
lease:
- SIGKILL to successor readiness: 19.5–19.6 s against the proposed 60 s target;
- acknowledgement latency with a 1 s flush: p50 549 ms, p99 1048 ms;
- a death was acknowledged in 44 ms;
- no acknowledged input was lost.
**M7 exit criteria are met locally.** Container, CI and cluster execution have not
run. Host-loss durability is M8.
Next: M8.1, the host inventory and budgets.