From db793044167d1b81cea7f2a2a57a189711d0d683 Mon Sep 17 00:00:00 2001 From: Erik Grinaker Date: Thu, 5 Dec 2024 18:29:21 +0100 Subject: [PATCH] storage_controller: increase shard scan timeout (#10000) ## Problem The node shard scan timeout of 1 second is a bit too aggressive, and we've seen this cause test failures. The scans are performed in parallel across nodes, and the entire operation has a 15 second timeout. Resolves #9801. ## Summary of changes Increase the timeout to 5 seconds. This is still enough to time out on a network failure and retry successfully within 15 seconds. --- storage_controller/src/service.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/storage_controller/src/service.rs b/storage_controller/src/service.rs index 92ec58cb4d..083c78233a 100644 --- a/storage_controller/src/service.rs +++ b/storage_controller/src/service.rs @@ -789,7 +789,7 @@ impl Service { node_list_futs.push({ async move { tracing::info!("Scanning shards on node {node}..."); - let timeout = Duration::from_secs(1); + let timeout = Duration::from_secs(5); let response = node .with_client_retries( |client| async move { client.list_location_config().await },