From aa0e3f85e6cc67385f55f84d20dee5a739acd36e Mon Sep 17 00:00:00 2001 From: Nhat Nguyen Date: Wed, 4 Nov 2020 08:21:35 -0500 Subject: [PATCH] Increase timeout in testCleanUpShardFollowTasksForDeletedIndices (#64562) If the deleted index has N shards, then ShardFollowTaskCleaner can send N*(N-1)/2 requests to remove N shard-follow tasks. I think that's fine as the implementation is straightforward. The test failed when the deleted index has 8 shards. This commit increases the timeout in the test. Closes #64311 --- .../java/org/elasticsearch/xpack/ccr/IndexFollowingIT.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/plugin/ccr/src/internalClusterTest/java/org/elasticsearch/xpack/ccr/IndexFollowingIT.java b/x-pack/plugin/ccr/src/internalClusterTest/java/org/elasticsearch/xpack/ccr/IndexFollowingIT.java index 5b032118bc0..cca0190bdff 100644 --- a/x-pack/plugin/ccr/src/internalClusterTest/java/org/elasticsearch/xpack/ccr/IndexFollowingIT.java +++ b/x-pack/plugin/ccr/src/internalClusterTest/java/org/elasticsearch/xpack/ccr/IndexFollowingIT.java @@ -1389,7 +1389,7 @@ public class IndexFollowingIT extends CcrIntegTestCase { String action = ShardFollowTask.NAME + "[c]"; ListTasksResponse listTasksResponse = followerClient().admin().cluster().prepareListTasks().setActions(action).get(); assertThat(listTasksResponse.getTasks(), hasSize(0)); - }); + }, 60, TimeUnit.SECONDS); ensureNoCcrTasks(); }