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
I would like to add new options to the connection and reconnection setup to make it work more like the node.js lib. On the node lib you can set the server connection param to a host:port string or array of host:port strings. If the array is used the client cycles through the array until it finds a server that it can connect to. There is also an parameter to shuffle the order of the host:port strings before attempting to connect. This should have the effect of load balancing connections.
I should be able to implement the above while leaving the current usage intact. I see that the node lib retained it's separate host and port params when it added the server param. I'm letting you know in case one of you is already working on this feature.
Regards
The text was updated successfully, but these errors were encountered:
Hi,
I would like to add new options to the connection and reconnection setup to make it work more like the node.js lib. On the node lib you can set the server connection param to a host:port string or array of host:port strings. If the array is used the client cycles through the array until it finds a server that it can connect to. There is also an parameter to shuffle the order of the host:port strings before attempting to connect. This should have the effect of load balancing connections.
While I'm at it I will look into connecting to an alternative server when the connected server goes into lame duck mode. https://docs.nats.io/running-a-nats-service/nats_admin/lame_duck_mode
I should be able to implement the above while leaving the current usage intact. I see that the node lib retained it's separate host and port params when it added the server param. I'm letting you know in case one of you is already working on this feature.
Regards
The text was updated successfully, but these errors were encountered: