Skip to content

G2 S6: Mac-tail cluster re-capture (live kind stand)#164

Merged
brownjuly2003-code merged 13 commits into
mainfrom
infra/g2-s6-mac-tail-recapture
Jul 6, 2026
Merged

G2 S6: Mac-tail cluster re-capture (live kind stand)#164
brownjuly2003-code merged 13 commits into
mainfrom
infra/g2-s6-mac-tail-recapture

Conversation

@brownjuly2003-code

Copy link
Copy Markdown
Owner

Summary

  • Re-records demo_voiced.mp4/demo.cast/demo_transcript.txt live on the current kitchen-legend narration (fixed two real bugs found along the way: an unconfigured mc alias inside minio-0, and a ReplacingMergeTree double-count from a retried promotion).
  • G1 live smoke: real postgres:16 container, APPLY=1 verify_bv_order.sh, 17/17 PASS — transcript at docs/perf/bv-order-canonical-pg-smoke-2026-07-06.md.
  • Full live kind-cluster re-capture of demo_evidence.md §1-3, §9, §10, §12, §13 on a rebuilt hq-demo cluster against the current seed. Two explicit, stated substitutions (§12 hand-ran the DAG's commands instead of installing Argo Workflows; §13 used direct SQL instead of a dbt Job after it OOM'd) — not disguised as full runs.
  • B4 (§14/15, CDC via MaterializedPostgreSQL): found and fixed a real bug — cdc_setup.sql only granted rep_user CONNECT, but MaterializedPostgreSQL self-bootstraps its publication via CREATE PUBLICATION as that user, which needs CREATE on the DB. Both sections now carry a genuine live capture.
  • Live-benchmark re-capture in load-test-baseline.md (12 scenarios, ~25 min under heavy host contention — explicit ambient-noise caveat included so the numbers aren't mistaken for an engine regression).
  • E4 (2-pod Postgres control-plane profile): partial. Static verification is thorough and passes (helm lint clean, helm template --set replicaCount=2 correctly fails without both ADR 0010 gate halves, succeeds with both). The live 2-pod deployment could not complete — a fresh app image build stalled twice under severe, sustained shared-host contention (co-tenant container at up to 80% CPU, this session's own kind control-plane crash-looping). Documented honestly in docs/clickhouse-cutover-plan.md Phase 3 and ADR 0010 rather than faked.

All of this ran live against a real Mac kind stand via SSH (host shared with another project's containers, which were left untouched). Every section states its own capture method; nothing here is fabricated or backfilled.

Test plan

  • G1 live smoke: 17/17 PASS (real Postgres)
  • Live-benchmark: full 12-scenario capture completed
  • Live kind-cluster re-capture: §1-3/§9/§10/§12/§13/§14/§15 all live, substitutions stated explicitly
  • E4 live 2-pod deploy — blocked by host contention this session, static verification only (see PR summary)
  • CI on this PR

🤖 Generated with Claude Code

Julia Edomskikh and others added 13 commits July 6, 2026 08:08
MaterializedPostgreSQL self-bootstraps its publication with CREATE
PUBLICATION executed as the replication user, and Postgres requires
CREATE on the database for that. With CONNECT alone the replication
handler retry-loops on "permission denied for database ops" — the CH
database appears but carries no slot, no publication and no tables.
Found live on the hq-demo kind stand 2026-07-06; the fan-out variant
(fanout/03_cdc_setup.sql) always carried the equivalent grant.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…-branch fan-out)

Both sections now carry live output from the hq-demo kind stand
(2026-07-06). §14: snapshot through the WAL pipeline (50/200/20/80),
slot ops active with advancing flush LSN, publication with 4 tables,
promotion collapsing to the same pg_ops__* hub counts as the §10 pull
pass, live INSERT/UPDATE/DELETE round-trip, count()-vs-column-read
tombstone semantics note, and the two-pass story (contention first,
then the deterministic GRANT CREATE root cause fixed in cdc_setup.sql).
§15: two per-branch Postgres DBs, two auto-named publications and
slots, 10/30 + 8/20 snapshots, 12-second edit propagation with
column-level detail, and a 0/0 cross-branch isolation check.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ion race

Commit 1784d5e (B2-mp4 re-record, prepared in a parallel working session)
was cut from a pre-2ed9ea3 copy of demo_evidence.md and unintentionally
reverted §14/§15 to the earlier attempted-blocked account, and stamped
the header with "§14/15 did not complete". Re-apply the full live
capture from 2ed9ea3 verbatim and reword the header note to match
reality (blocked first pass, then GRANT CREATE root cause found and the
sections captured live). No other B2 content from 1784d5e is touched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

DORA Metrics

  • Window: last 30 days
  • Branch: main
  • Deployment frequency: 87 total / 20.3 per week
  • Lead time for changes: avg 0.45h / median 0.0h
  • Change failure rate: 59.77% (52/87)
  • MTTR: n/a across 0 incident(s)

MTTR note: No failed mainline CI runs in the selected window.

@brownjuly2003-code brownjuly2003-code merged commit fa4ba22 into main Jul 6, 2026
19 checks passed
@brownjuly2003-code brownjuly2003-code deleted the infra/g2-s6-mac-tail-recapture branch July 6, 2026 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant