From de2e5b24a8004c628f5771de4c5bedd7022edb95 Mon Sep 17 00:00:00 2001 From: Sridhar Gaddam Date: Mon, 3 May 2021 20:20:41 +0530 Subject: [PATCH] Increase connect-timeout in benchmark tests Currently, while using subctl benchmark tests, the client pod is using a connect-timeout of 10ms which is too low. It was working fine in KIND Clusters as the latency between the clusters is generally less, but in an OnPrem vs Public cluster environments the benchmark tests it was creating issues. This PR fixes the issue by increasing the connect-timeout value to 10 secs. Signed-Off-by: Sridhar Gaddam (cherry picked from commit 3a6730cb36e99ee633f3ce01a3acc99e9906b17d) --- test/e2e/framework/network_pods.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/framework/network_pods.go b/test/e2e/framework/network_pods.go index 1aef5c544..af0b3089b 100644 --- a/test/e2e/framework/network_pods.go +++ b/test/e2e/framework/network_pods.go @@ -345,7 +345,7 @@ func (np *NetworkPod) buildThroughputClientPod() { {Name: "TARGET_PORT", Value: strconv.Itoa(np.Config.Port)}, {Name: "CONN_TRIES", Value: strconv.Itoa(int(np.Config.ConnectionAttempts))}, {Name: "RETRY_SLEEP", Value: strconv.Itoa(int(np.Config.ConnectionTimeout))}, - {Name: "CONN_TIMEOUT", Value: strconv.Itoa(int(np.Config.ConnectionTimeout))}, + {Name: "CONN_TIMEOUT", Value: strconv.Itoa(int(np.Config.ConnectionTimeout*1000))}, }, }, },