You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(gate,health): exact seeded-interval query check and honest probe budget
Review fixes (PR #218):
- The query phase asks for the exact deterministic seeded interval
[FirstWindow, LastWindow+5m) — exactly 2016 windows, inside the engine
read-range cap, excluding the protocol's live windows — instead of a
trailing window with boundary-trimmed expectations. HOT_RETENTION_DAYS=8
in the gate config keeps every seeded window alive through the run.
Completeness now asserts extra == 0 as well as missing == 0; the extra
count was previously computed and discarded.
- READY_AGGREGATE_DISK_BUDGET_MB returns to the real tier allocation
(2304 MB) and READY_MAX_AGGREGATE_DISK_RATIO defaults to 1.0: readiness
fails exactly at the tier boundary instead of using a synthetic 2560
denominator to fake the same trip point. Boundary pinned by tests at
one byte below, exactly at, and one byte above the tier.
- Comment wording: 4 MiB/window projects to 4.5 GiB, which exceeds the
4.0 GiB main tier rather than merely consuming it.
Copy file name to clipboardExpand all lines: CLAUDE.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -701,8 +701,8 @@ Thresholds (`0` disables that probe):
701
701
|`READY_MAX_FINALIZE_FAILURE_STREAK`| 3 | Same shape, on the finalizer. |
702
702
|`READY_MAX_ADMISSION_RATIO`| 0.9 | Below the 0.95 the DLQ/pipeline probes use: the writer's admission bound is what turns an Export into `RESOURCE_EXHAUSTED`, so readiness says "stop sending" before clients are refused, not while they are. |
703
703
|`READY_MAX_DELTA_LOG_AGE_S`| 1800 | 2× (`WindowSize` 5m + `AllowedLateness` 10m). A window is finalizable 900s after it opens, so a healthy oldest entry tops out just past 900s plus one finalize tick. |
704
-
|`READY_AGGREGATE_DISK_BUDGET_MB`|2560|`aggregate.db`'s share of the 8 GiB data budget (#201 Q1). The disk watchdog enforces the **volume**; this enforces the **tier**, so a runaway aggregate file is visible before it eats another tier's allocation. |
705
-
|`READY_MAX_AGGREGATE_DISK_RATIO`|0.9|Warn inside the tier before the volume-level ladder starts shedding. |
704
+
|`READY_AGGREGATE_DISK_BUDGET_MB`|2304|`aggregate.db`'s share of the 8 GiB data budget (#201 Q1). The disk watchdog enforces the **volume**; this enforces the **tier**, so a runaway aggregate file is visible before it eats another tier's allocation. |
705
+
|`READY_MAX_AGGREGATE_DISK_RATIO`|1.0|Readiness fails exactly at the tier allocation. Full-density steady state (~0.92 of the tier) is legitimate; earlier warning is the volume-level watchdog ladder's job. |
0 commit comments