From e67c84fa14d328bc2733bcc0e354ec759b8726a1 Mon Sep 17 00:00:00 2001
From: qdrant-cloud-bot <111755117+qdrant-cloud-bot@users.noreply.github.com>
Date: Thu, 3 Sep 2026 11:18:03 +0200
Subject: [PATCH] Fix flaky WAL filter-resolution test by disabling aggressive
 flush (#10446)

The test asserts live WAL contents after applied updates, but the default
fixture uses flush_interval_sec = 0 so the flush worker can truncate
earlier rewritten records before the assertion runs.

Fixes #10423
---
 lib/collection/src/tests/wal_recovery_test.rs | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/lib/collection/src/tests/wal_recovery_test.rs b/lib/collection/src/tests/wal_recovery_test.rs
index 70284b215d..0a8b286cdd 100644
--- a/lib/collection/src/tests/wal_recovery_test.rs
+++ b/lib/collection/src/tests/wal_recovery_test.rs
@@ -1183,7 +1183,11 @@ async fn test_filter_ops_resolved_to_ids_in_wal() {
     let _ = env_logger::builder().is_test(true).try_init();
     let collection_dir = Builder::new().prefix("test_collection").tempdir().unwrap();
 
-    let config = create_collection_config();
+    // This test inspects live WAL contents after applied updates. The default
+    // fixture uses `flush_interval_sec = 0`, so the flush worker can ack and
+    // truncate earlier records before we read them (issue #10423).
+    let mut config = create_collection_config();
+    config.optimizer_config.flush_interval_sec = 3600;
     let collection_name = "test".to_string();
 
     let update_runtime = Handle::current();