Task · TSO-0197

Bound expanded startup replay memory without stranding accepted ingress work

Description

Follow-up to TSO-0192 (diagnose OOM restarts and propose a fix). Independent read-only process/workload diagnosis identifies retained startup-replay metric-operation tapes and cloned logs as the dominant observed heap-pressure mechanism. The existing disk-encoded WAL byte window and receipt-count ceiling do not reserve aggregate expanded process memory. Restarting or reducing disk capacity alone can leave already-accepted work unable to drain. Diagnosis is complete, but no remediation or numerical safe budget was implemented or proven. This source fix needs separately commissioned guarded work and protected offline workload/cgroup evidence; no induced live traffic, forced promotion, WAL deletion or undocumented telemetry suppression is authorized by the diagnosis.

Acceptance Criteria

Definition of Done

Implementation Notes

Owner approved design first on 2026-10-13. TSO-0197.01 (freeze the bounded replay-memory design and implementation proof packet) is the separately commissioned prerequisite. Implementation and all four parent acceptance criteria remain open; no new production capture or cleanup is commissioned. Retained evidence cannot establish a safe measured process budget. The design must identify missing workload inputs and preserve future implementation attempt lineage.

loop32 completed TSO-0197.01 (freeze bounded replay-memory design and proof packets) under the approved design-only exception. Canonical independent PASS: /Users/rob/repos/tailscale2otel/codex/loop32/design-review.md. Two design corrections, zero implementation attempts. All four parent criteria remain unchecked, no remediation or numerical safe cap proven. Resume only after protected original-shape/representative ordinary-envelope prerequisites and separately commissioned implementation; retain one serial owner across frozen storage/preparation/delivery seams. TSO-0197.02 (preserve required delta first-cover effects across failed scheduled collection) records a source-grounded inferred failure-path finding; negative reproduction and repair remain uncommissioned.

2026-11-01 owner commissioned implementation for loop33 (both TSO-0197 and TSO-0197.02), plus a read-only read of ingress WAL entry-size and shape statistics from a lab pod through the tailnet-proxied context, no writes, to supply the missing W1 workload input. One serial senior owner across the frozen storage/preparation/delivery seams, per the loop32 design.

loop33: implementation commissioned, but W1 access prerequisite cannot be completed under current read-only command grant: distroless exporter lacks permitted inspection utilities, sidecar subPath excludes WAL. No diagnostic container, mount change, restart or synthetic sizing substitute attempted. Resume after owner-authorised read-only offline snapshot or diagnostic access supplies protected joint original-shape and ordinary/cgroup envelope evidence. Parent implementation not started, no cap or progress claim.

loop33 closeout park reaffirmed: owner evidence/access blocker remains. The authorized read-only WAL utilities cannot execute in the distroless exporter; the available sidecar does not mount that WAL. No cluster mutation was attempted. Resume the selected bounded design with an owner-authorized read-only WAL snapshot/diagnostic mechanism or protected supplied joint-shape and ordinary-memory-envelope evidence, then the same serial senior lane. No safe-cap or live-loss conclusion is established.

References

View the source file on GitHub