fe8d0c87e7
Implements tmp/tidaldb-fleet-hardening (20 planned tasks + 2 found by measurement). Ring 0 — restore verification. .woodpecker.yaml step pods ran at the namespace default of 1500m/2Gi, which OOMKilled a prior pipeline and starved the release gate past its budget. Both push-path steps now declare backend_options.kubernetes.resources as two YAML anchors declared once on their first consuming step. The values are CALIBRATED against measured free node capacity, not against the LimitRange max: `requests: cpu 2` (this roadmap's original figure) fits on NO node and would sit Pending forever, because `ci-build-bounds` grants permission and the nodes supply capacity, and those are not the same thing. The `nightly` cron described in this file for 216 days was never created, so tier-3 chaos, the fault classes, mTLS and the PITR test produced exactly zero signal while reading like standing coverage. nightly-chaos and nightly-security-ops now alias the anchors and have budgets matching the gate (their 120/90 were TIGHTER on the same runner, so they would have failed nightly for a budget reason, not a correctness one). nightly-soak is REMOVED, not scheduled: it drives 1000 rps for 600s gating on p99 <= 250ms, and the best node has 1700m free CPU, so it would fail on starvation rather than regression — manufacturing a nightly false alarm. Its commands move verbatim to docs/runbooks/nightly-soak.md. Ring 1 — four fabrications removed from the wire. - scatter_merge sorted and truncated without re-stamping rank, so /feed and /search returned 1,1,2 under full placement. Reuses merge_cross_shard's existing stamp; asserted on BOTH the multi-group merge path and the single-group [only] fast path that bypasses it. - aggregate_region_row's None arm invented `applied_events: 0` plus a deficit derived from it. applied_events/lag_events are now Option<u64>, null on the wire. leader_last_seq was also unwrap_or(0), so a node that could not reach the LEADER computed 0 - applied = 0 for every region and reported a converged cluster it had never measured — a fabrication pointing the dangerous way. - tidalctl inferred NO REPORT from `applied == 0 && lag > 0`. That heuristic was actively hiding the PVC-wipe shape: a measured zero with a real deficit rendered as "no report" instead of BEHIND. Now read off the wire; converged exits 0, partitioned still exits nonzero. - /sharded/* answered 201/204 for single-copy writes with nothing anywhere saying so. Now requires `x-tidal-ack: local`, rejecting with 400 via the existing invalid_input path. Six call sites migrated, not the two this roadmap predicted — including docs/runbooks/cluster.md §16.3, which told operators to run a quorum-write probe via POST /sharded/items. That probe cannot verify quorum: the surface applies locally with no WAL append. It was used as the safety check between every step of a staged deploy earlier today. Ring 2 — observability. JSON_LOGS was already implemented and the deployment simply never asked for it; the StatefulSet now sets it, plus TIDAL_SERVICE_NAME=tidaldb because enabling it silently renames the VictoriaLogs `service` stream field and would have blinded every query keyed on it. Adds tidaldb_usearch_replicated_vectors_total, incremented on BOTH the origin (wal_blob_first -> Ok(Some)) and the follower apply path — counting only the origin would mean each vector lands on exactly one node, replicas never agree, and the alert built on it pages forever. Found by measurement, not planned: the 401 path discarded every fact about every rejection. Traefik has served 101,858 rejected requests to the public ingress — 87.6% of all its traffic — with no record of who or why anywhere. unauthorized_response now emits reason (missing_token vs invalid_token, the distinction that separates a scanner from a rotation that missed a consumer) and the forwarded client. The token is never logged. Also: scripts/restore-fleet.sh --cluster started the soak monitor while deliberately leaving its gate suspended, orphaning a watcher that has reported "0/30 green nights" for 13 days. The pair now moves together. Doc-guard's three-warning backlog is cleared with real backfill for M4/M6/M12. Verified: fmt clean; clippy 5 crates 0 new warnings (74 vs 74 baseline, counted in a detached worktree at HEAD); lib 2110 passed; cluster_sharding 5; cluster_runbook 10; tidalctl 38; doc-guard 0 warnings. Playwright 32/34 with the two remaining failures asserting the rank fix against the not-yet-rolled image — they are the post-deploy proof.
48 lines
2.4 KiB
Markdown
48 lines
2.4 KiB
Markdown
# m12p6 — TLS scale-up + HNSW graph persistence (✅ COMPLETE 2026-06-16)
|
|
|
|
Landed across `8e39ee1`, `4db3f1e`, `a039955` (2026-06-14→15), then `727fbfc`
|
|
and `44ec878` (2026-06-16). Changelog:
|
|
[CHANGELOG.md](../../../CHANGELOG.md). Milestone index: [README.md](README.md).
|
|
Backfilled record.
|
|
|
|
## What shipped
|
|
|
|
1. **Elasticity over REAL mTLS on k8s, for the first time.** A genuine
|
|
`kubectl scale 3→5` exercised seed-join over mTLS on `kind`: joiners flip
|
|
Ready in ~13 s via the m12p5 idle-readiness heartbeat, auto-promote to Voter,
|
|
reach full content parity at lag 0, and scale-down loses **zero acknowledged
|
|
DATA writes**.
|
|
2. **A six-bug chain fixed to get there** — each one a separate way TLS turns a
|
|
working plaintext path into a silent failure:
|
|
- `https://` seed scheme (a plaintext seed URL against a TLS listener),
|
|
- rustls `CryptoProvider` install order (must be installed up front),
|
|
- a headless seed Service (so a joiner can resolve peers before joining),
|
|
- cold-handshake poll timeout,
|
|
- two-tier cert-manager PKI,
|
|
- the `grpc_tls_for` CA fallback for a joiner **not yet in the topology** —
|
|
the bootstrap paradox: a node needs TLS to join, and joining is what puts it
|
|
in the topology TLS is derived from.
|
|
3. **HNSW graph persistence + bounded SIGTERM drain** (`a039955`). Boot loads the
|
|
persisted graph instead of rebuilding it, and a suspect graph is **skipped on
|
|
reseed-pending close** rather than trusted — the fail-closed choice: a
|
|
rebuild costs time, a silently corrupt graph costs correctness.
|
|
4. **7th edge** (`44ec878`): correct reseed seqno alongside the suspect-graph
|
|
skip (rc11), plus the rc8+rc9 6-bug k3s 3-shard cluster repair (`727fbfc`).
|
|
|
|
## Evidence
|
|
|
|
- `tidal/tests/m12p6_graph_persistence.rs` (1),
|
|
`tidal/tests/m12_reseed_term_marker.rs` (4).
|
|
- `tidal-server/tests/cluster_region.rs` (14).
|
|
- [docs/profiling/m12-cluster-deploy-findings.md](../../profiling/m12-cluster-deploy-findings.md)
|
|
— the k3s deploy record, incl. the clean-slate 100k/1536 re-seed and the
|
|
workspace test tallies at rc8.
|
|
|
|
## Carried forward
|
|
|
|
The reseed/readiness surface kept needing repair after M12 closed —
|
|
`c8ea05b`, `fe56d1b`, `973f073` (2026-06-18), `da736b8` (2026-08-20),
|
|
`5b3cfe5` and `7450cc7` (2026-08-21). Read m12p6 as "the scale-up path was
|
|
proven once, end to end, over real TLS", not as "the reseed state machine was
|
|
finished".
|