Update AccountManager._getNodeClient() to parallel the test connection calls and reduce the total time it takes to fail for load balancer IP logic

[jeromy-cannon]

During testing a 10 node configuration Alex believed the process was hanging. Upon examination of the logs, it was using the default LoadBalancer configuration deployed to Latitude, but Latitude was blocking the calls. Each node configuration for the node client was taking 2 minutes. So, it would have been a 20 minute wait every time it had to create a client node, which is unacceptable. He was able to override the values file and set it to ClusterIP and avoid the issue as a workaround.

Tasks

Preview Give feedback

1. Update AccountManager._getNodeClient() to parallel the configureNodeAccess() calls
2. Reduce the constants.NODE_CLIENT_PING_MAX_RETRIES to 5
3. Reduce the constants.NODE_CLIENT_PING_RETRY_INTERVAL to 10 seconds

[swirlds-automation]

🎉 This issue has been resolved in version 0.33.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[swirlds-automation]

🎉 This issue has been resolved in version 0.33.0 🎉

The release is available on:

• npm package (@release-0.33.x dist-tag)
• GitHub release

Your semantic-release bot 📦🚀