You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, every registration (and now metric push) initiates a new TCP/IP connection to the orchestrator. I wonder if it would be more efficient if each node set the keep-alive setting on the http connection and reused their socket connection for each interaction with the orchestrator. It is possible this will have no effect or cause other issues, but it is at least worth exploring.
The text was updated successfully, but these errors were encountered:
Currently, every registration (and now metric push) initiates a new TCP/IP connection to the orchestrator. I wonder if it would be more efficient if each node set the keep-alive setting on the http connection and reused their socket connection for each interaction with the orchestrator. It is possible this will have no effect or cause other issues, but it is at least worth exploring.
The text was updated successfully, but these errors were encountered: