From b1818364d52baf947defaadc2085f7433936187b Mon Sep 17 00:00:00 2001 From: Zeying Zhu Date: Mon, 20 Apr 2026 09:38:42 -0400 Subject: [PATCH] chore(compose): enable --enable-schema-eviction in precompute quickstart MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The quickstart precompute compose was missing `--enable-schema-eviction`, so Expired schemas (produced by a `StreamingConfig` swap that removed an agg_id, or by `POST /api/v1/db/schemas/:id/expire`) stayed resident in the registry forever and their data never got dropped from the store. The e2e that added retire/expire endpoints in #42 surfaced this: calling `force_expire` flipped the schema's status immediately but the data kept hanging around until a backend restart (which wipes the registry entirely — the opposite of what the §5 service is designed to manage). Also sets `--schema-eviction-poll-secs=60` (down from the 300s default) to make the eviction visible inside a demo run. Production deployments should raise this. Co-Authored-By: Claude Opus 4.7 (1M context) --- asap-quickstart/docker-compose-precompute.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/asap-quickstart/docker-compose-precompute.yml b/asap-quickstart/docker-compose-precompute.yml index e0353ada..3d9a020c 100644 --- a/asap-quickstart/docker-compose-precompute.yml +++ b/asap-quickstart/docker-compose-precompute.yml @@ -128,6 +128,12 @@ services: - "--query-language=PROMQL" - "--lock-strategy=per-key" - "--forward-unsupported-queries" + # §5/§10 sketch-DB lifecycle. Without --enable-schema-eviction, + # Expired schemas stay resident forever and their data never + # gets dropped from the store; the 60s poll is tuned for demo + # visibility, not production — tune up for real deployments. + - "--enable-schema-eviction" + - "--schema-eviction-poll-secs=60" healthcheck: test: ["CMD-SHELL", "bash -c 'echo > /dev/tcp/localhost/8088' 2>/dev/null || exit 1"] interval: 10s