From 94c0c84b77a99980ddbaa304c858db263e65bcb5 Mon Sep 17 00:00:00 2001 From: Rene Groeschke Date: Tue, 30 Sep 2025 10:11:22 +0200 Subject: [PATCH] [Build] Aggressively increase gradle based Test Cluster startup timeout We see plenty of errors due to a cluster not starting up. This is likely a combination of parallelism, memory pressure and to little timeout. This is aggressively increasing the timeout from 40 to 120s while we will monitor if the overall flakyness in ci is reduced --- .../elasticsearch/gradle/testclusters/ElasticsearchCluster.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-tools/src/main/java/org/elasticsearch/gradle/testclusters/ElasticsearchCluster.java b/build-tools/src/main/java/org/elasticsearch/gradle/testclusters/ElasticsearchCluster.java index 0248c848e0988..c2a4fc5a81ec2 100644 --- a/build-tools/src/main/java/org/elasticsearch/gradle/testclusters/ElasticsearchCluster.java +++ b/build-tools/src/main/java/org/elasticsearch/gradle/testclusters/ElasticsearchCluster.java @@ -64,7 +64,7 @@ public class ElasticsearchCluster implements TestClusterConfiguration, Named { private static final Logger LOGGER = Logging.getLogger(ElasticsearchNode.class); - private static final int CLUSTER_UP_TIMEOUT = 40; + private static final int CLUSTER_UP_TIMEOUT = 120; private static final TimeUnit CLUSTER_UP_TIMEOUT_UNIT = TimeUnit.SECONDS; private final AtomicBoolean configurationFrozen = new AtomicBoolean(false);