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:
@@ -2485,3 +2485,52 @@ Only clean-to-v1 and exact-v1 restart are supported migration paths at this gate
|
||||
stale-binary run was discarded and the mutation was rerun.
|
||||
- Not executed: clones across separate PostgreSQL clusters or hosts, Docker, the
|
||||
Gitea CI, and cluster runs.
|
||||
|
||||
## M7.9b upgrade barrier and durability qualification - 2026-09-29
|
||||
|
||||
- Every M7.9b change is in the Linux PostgreSQL build or in docs. Windows was not
|
||||
rerun; its 59/59 from M7.9a still covers the portable code, which is unchanged.
|
||||
- WSL Linux `checks` set (GCC14 Debug and Release, clang19 analysis, clang19
|
||||
ASan/UBSan) passed CTest 59/59 each. The format check passed.
|
||||
- The PostgreSQL suites passed in GCC Release, clang-tidy analysis and ASan/UBSan.
|
||||
After the mutation run, one host test was corrected: `unrestorable_head_quarantines`
|
||||
now retains its build, so the quarantine it checks again comes from recovery
|
||||
rather than acquisition. Release and analysis were rebuilt and rerun green after
|
||||
that change. The ASan build compiled with it, but its full run predates it.
|
||||
- Harness: upgrade paths now end at 1..8. The populated v6 database upgrades to v8.
|
||||
Version and checksum drift checks include v8.
|
||||
- Migration and barrier test (database `evo_online`, created at v7 from the
|
||||
checked-in files):
|
||||
- A pre-v8 writer with a build-less lease published ticks 1..20 (with the
|
||||
death).
|
||||
- An `apply.sql` run with an invalid v8 checksum failed. It left history 1..7,
|
||||
no `retired_at` column and no four-argument acquire. The writer renewed and
|
||||
published ticks 21..40.
|
||||
- The real migration then reached v8 while the writer held its lease, and the
|
||||
writer published ticks 41..60.
|
||||
- Barrier refusals: the runtime cannot call it (42501), and retiring the last
|
||||
current build is refused (22023).
|
||||
- After the barrier (1 lease fenced), the old writer's publication and renewal
|
||||
were fenced. Build-less acquisition returned EVL06, and acquisition with b1
|
||||
returned unsupported.
|
||||
- A b2 lease publishing a link that names b1 was refused as unsupported.
|
||||
- A b2 `evo-server` became ready at epoch 3 from committed tick 60 and
|
||||
acknowledged through tick 90. Its final head is built by b2.
|
||||
- The audit passes with both builds retained, and reports unsupported at
|
||||
sequence 0 with only b2.
|
||||
- A b1 `evo-server` quarantined (exit 4) without becoming ready, and the head
|
||||
was unchanged.
|
||||
- Qualification: see engineering/DURABILITY_QUALIFICATION.md. SIGKILL to ready
|
||||
took 19.5–19.6 s under the production lease in all three builds (the 60 s
|
||||
target is asserted). Acknowledgement latency p50 was about 549 ms and p99
|
||||
about 1048 ms. No acknowledged input was lost, and one durable death was
|
||||
recorded across five owners.
|
||||
- Mutations (each restored and rebuilt). Each was caught:
|
||||
- no retired-build trigger;
|
||||
- no build check in four-argument acquisition;
|
||||
- no barrier check in build-less acquisition;
|
||||
- a barrier that does not fence holders;
|
||||
- a host that retries an unsupported acquisition instead of quarantining.
|
||||
The migration test caught this one after the host-test correction.
|
||||
- Not executed: Docker, the Gitea CI, cluster runs, a separate database host, and
|
||||
host or storage loss (M8).
|
||||
|
||||
Reference in New Issue
Block a user