From 21510c7ce6f818cf0eba338abe267a32b33cc3f9 Mon Sep 17 00:00:00 2001
From: Julian Huang <jhuang@altinity.com>
Date: Wed, 2 Sep 2026 11:09:46 -0400
Subject: [PATCH] Set CAS-S3 test GC interval to 120s for a CI wall-time
 experiment

DO NOT MERGE. Compare ASan CAS-S3 shard duration against the 5s timeout, 60s OOM, and GC-off runs.

Co-authored-by: Cursor <cursoragent@cursor.com>
---
 .../cas_s3_storage_policy_for_merge_tree_by_default.xml    | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/tests/config/config.d/cas_s3_storage_policy_for_merge_tree_by_default.xml b/tests/config/config.d/cas_s3_storage_policy_for_merge_tree_by_default.xml
index d74dfe173095..5a64ca840d37 100644
--- a/tests/config/config.d/cas_s3_storage_policy_for_merge_tree_by_default.xml
+++ b/tests/config/config.d/cas_s3_storage_policy_for_merge_tree_by_default.xml
@@ -18,11 +18,10 @@
                 <secret_access_key>clickhouse</secret_access_key>
                 <!-- Real server-local scratch dir for the write-buffer spill. -->
                 <cas_scratch_path>cas_s3_scratch/</cas_scratch_path>
-                <!-- Background GC pacing: the incarnation protocol's fence/recheck handshake
-                     replaces the old grace window (M-W D-W5); a short interval so reclamation
-                     happens during the run. -->
+                <!-- DO NOT MERGE. Experiment: 120s GC interval to compare ASan CAS-S3
+                     stateless wall time vs 5s (timeout), 60s (OOM), and GC off. -->
                 <cas_gc_enabled>1</cas_gc_enabled>
-                <cas_gc_interval_sec>5</cas_gc_interval_sec>
+                <cas_gc_interval_sec>120</cas_gc_interval_sec>
             </cas_s3>
             <!-- Optional local filesystem cache in front of the cacheless CA-S3 disk (mirrors how plain-s3
                  backs its policy with `cached_s3`). Validated: once warm it serves reads from local disk