mikebridge commented on PR #42760: URL: https://github.com/apache/superset/pull/42760#issuecomment-5746361513
## Flag-on soak: PASS at `f934d64d` This completes the third hold-lift condition. Evidence summary; the full report with the harness, matrix and raw counters is in our spec repo. **Setup.** Isolated stack built from this PR's head, `SEMANTIC_LAYERS` + `SEMANTIC_LAYER_CONTAINMENT_CACHE` on at boot, an opted-in reference provider backed by a real SQL database, and — importantly — a **separate Redis client/db for `DISTRIBUTED_COORDINATION_CONFIG`** from `DATA_CACHE_CONFIG`, so the split-store path is the one under test. Every API answer was compared against the equivalent direct SQL result. **Timed run (4 concurrent clients, 1,210 s).** - **4,386 responses: all HTTP 200, all matching the independent SQL answer. Zero wrong answers, zero request errors.** - 880 forced refreshes racing normal reads; 3,466 HIT / 920 MISS at the API layer (API MISS also covers force-bypass and ordinary result-cache responses, so it is not the containment service's `miss` counter). - Matrix covered exact-key repeats, narrowed time ranges contained in a cached wider range, coarser-grain and filter subsets, and forced refreshes under concurrency. **Reader-side fence.** Four deterministic same-key writer-takeover rounds: **12/12 correct**. Containment counters for the window: `hit` 3,470, `miss` 2, `bypass` 968, **`fence_reject` 31**, plus `lookup_failure` 11, `coordination_failure` 16, `store_failure` 16 — those three are the *expected* observations from deliberately induced stale-writer and outage faults, and no incorrect answer was served in any of them. **Controls.** Flag off → no semantic caching (three bypass counters, zero semantic hits or stores). A Redis restart mid-soak recovered with no wrong answers. **Scope of the claim.** This is bounded validation for this SHA against the reference provider workload, not a proof for every provider or workload. Exact-head CI, including `test-semantic-cache-coordination`, is green. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
