From a97489be754fc2fcbe37086d42e41487d3cbb6e6 Mon Sep 17 00:00:00 2001 From: Gabor Gevay Date: Tue, 8 Sep 2026 13:24:00 +0200 Subject: [PATCH] parallel-workload: ignore the RTR timeout in ExplainFilterPushdownAction SelectAction already treats "timed out before ingesting the source's visible frontier when real-time-recency query issued" as an ignorable error, because a session with real-time recency enabled can legitimately hit the RTR timeout. ExplainFilterPushdownAction issues EXPLAIN FILTER PUSHDOWN FOR SELECT ... on the same sessions and waits for the source the same way, but did not list the error, so the RTR timeout failed the whole workload (nightly 18001 and 18005, 2026-08-09; tracked under SS-303). Co-Authored-By: Claude Fable 5.1 --- misc/python/materialize/parallel_workload/action.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/misc/python/materialize/parallel_workload/action.py b/misc/python/materialize/parallel_workload/action.py index 6a008fc235834..c5678150d34c6 100644 --- a/misc/python/materialize/parallel_workload/action.py +++ b/misc/python/materialize/parallel_workload/action.py @@ -6249,6 +6249,9 @@ def errors_to_ignore(self, exe: Executor) -> list[str]: 'is not allowed from the "mz_catalog_server" cluster', # Scanning persist part stats can outrun statement_timeout. "canceling statement due to statement timeout", + # Under real-time recency the EXPLAIN waits for the source + # like a SELECT does, and can hit the RTR timeout (SS-303). + "timed out before ingesting the source's visible frontier when real-time-recency query issued", ] ) if exe.db.complexity == Complexity.DDL: