Closed achimnol closed 2 years ago
There are two load balancing points in the client SDK:
random.shuffle
the endpoint list.Currently the console-server uses the first method because it instantiates and discards API session objects per HTTP request taking the credential information from the HTTP cookie. So we are postponing this issue as a future work with no deadline.
Instead, we decided to improve the wsproxy related components to spread their connections to multiple manager endpoints, while keeping its the cookie-based session handlers interacting with the console server.
Closing it as stale.
Currently it randomize the selection of endpoints upon startup and rotates the endpoints only when there are connection failures. Let's extend it to support endpoint rotation based on timing and connection counts.