From 0dd5340960a9ca5a122c3974add537ef1762328d Mon Sep 17 00:00:00 2001
From: Sameer Kumar Subudhi <sameer.subudhi@lightcurve.io>
Date: Thu, 4 Apr 2024 16:39:50 +0200
Subject: [PATCH] :gear: Increase API endpoint invoke retry time to reduce
 pressure on the node

---
 docker/example.env                                      | 2 +-
 docs/antora/modules/ROOT/pages/configuration/index.adoc | 4 ++--
 ecosystem.config.js                                     | 2 +-
 services/blockchain-connector/README.md                 | 2 +-
 services/blockchain-connector/config.js                 | 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docker/example.env b/docker/example.env
index 12f367ec66..6c8ac97176 100644
--- a/docker/example.env
+++ b/docker/example.env
@@ -40,7 +40,7 @@
 # WS_SERVER_PING_INTERVAL=3000
 # WS_SERVER_PING_INTERVAL_BUFFER=1000
 # ENDPOINT_INVOKE_MAX_RETRIES=3
-# ENDPOINT_INVOKE_RETRY_DELAY=50
+# ENDPOINT_INVOKE_RETRY_DELAY=500
 # CONNECTOR_EXIT_DELAY_IN_HOURS=0
 
 # Moleculer jobs configuration 
diff --git a/docs/antora/modules/ROOT/pages/configuration/index.adoc b/docs/antora/modules/ROOT/pages/configuration/index.adoc
index ceed08825c..1e87a42cc0 100644
--- a/docs/antora/modules/ROOT/pages/configuration/index.adoc
+++ b/docs/antora/modules/ROOT/pages/configuration/index.adoc
@@ -442,8 +442,8 @@ By default, it is set to `3`.
 | `ENDPOINT_INVOKE_RETRY_DELAY`
 | number
 | Delay (in milliseconds) between each endpoint invocation request retry.
-By default, it is set to `50`.
-| 50
+By default, it is set to `500`.
+| 500
 
 | `CONNECTOR_EXIT_DELAY_IN_HOURS`
 | number
diff --git a/ecosystem.config.js b/ecosystem.config.js
index 6613bcda43..8c82dce0e5 100644
--- a/ecosystem.config.js
+++ b/ecosystem.config.js
@@ -133,7 +133,7 @@ module.exports = {
 				// WS_SERVER_PING_INTERVAL=3000,
 				// WS_SERVER_PING_INTERVAL_BUFFER=1000,
 				// ENDPOINT_INVOKE_MAX_RETRIES: 3,
-				// ENDPOINT_INVOKE_RETRY_DELAY: 50,
+				// ENDPOINT_INVOKE_RETRY_DELAY: 500,
 				// CONNECTOR_EXIT_DELAY_IN_HOURS: 0,
 				// JOB_INTERVAL_CACHE_CLEANUP: 0,
 				// JOB_SCHEDULE_CACHE_CLEANUP: '0 */12 * * *',
diff --git a/services/blockchain-connector/README.md b/services/blockchain-connector/README.md
index ce074adf15..f1b313de1f 100644
--- a/services/blockchain-connector/README.md
+++ b/services/blockchain-connector/README.md
@@ -40,7 +40,7 @@ A list of the most commonly used environment variables is presented below:
 - `WS_SERVER_PING_INTERVAL`: Interval (in milliseconds) at which the WS server checks for liveliness of all the connected clients. This should not be modified unless explicitly recommended by the development team. By default, it is set to `3000`.
 - `WS_SERVER_PING_INTERVAL_BUFFER`: A conservative assumption of the latency (in milliseconds) for WS server pings to arrive at the client. By default, it is set to `1000`.
 - `ENDPOINT_INVOKE_MAX_RETRIES`: Maximum number of endpoint invocation request retries to the node. By default, it is set to `3`.
-- `ENDPOINT_INVOKE_RETRY_DELAY`: Delay (in milliseconds) between each endpoint invocation request retry. By default, it is set to `50`.
+- `ENDPOINT_INVOKE_RETRY_DELAY`: Delay (in milliseconds) between each endpoint invocation request retry. By default, it is set to `500`.
 - `CONNECTOR_EXIT_DELAY_IN_HOURS`: Delay (in hours) after which the blockchain-connector microservice exits. The service should restart automatically if deployed using Docker or PM2. To be removed eventually. To enable it, set it higher than `0`. By default, it is set to `0`.
 - `JOB_INTERVAL_CACHE_CLEANUP`: Job run interval to cleanup block cache. By default, it is set to `0`.
 - `JOB_SCHEDULE_CACHE_CLEANUP`: Job run cron schedule to cleanup block cache. By default, it is set to run every 12 hours (`0 */12 * * *`).
diff --git a/services/blockchain-connector/config.js b/services/blockchain-connector/config.js
index ad8864446f..3897e49206 100644
--- a/services/blockchain-connector/config.js
+++ b/services/blockchain-connector/config.js
@@ -121,7 +121,7 @@ config.apiClient = {
 	pingIntervalBuffer: Number(process.env.WS_SERVER_PING_INTERVAL_BUFFER) || 1000, // in millisecs
 	request: {
 		maxRetries: Number(process.env.ENDPOINT_INVOKE_MAX_RETRIES) || 3,
-		retryDelay: Number(process.env.ENDPOINT_INVOKE_RETRY_DELAY) || 50, // in millisecs
+		retryDelay: Number(process.env.ENDPOINT_INVOKE_RETRY_DELAY) || 500, // in millisecs
 	},
 };