Is it possible that I can trigger the client to reconnect on discovering a new cluster node?

[YanKawaYu]

Hi guys,

Now the client only reconnects when it encountered errors. So if I added a new node into my cluster, it won't have any traffic at all until some clients reconnect. I think it will cause a big problem when upgrading NATS cluster.

So if I can trigger the client to reconnect once it discovered a new node, then the problem will be solved.

Any ideas on this one? Really appreciate!

[derekcollison]

Sometimes clients want to connect to specific servers, but in general we recommend connecting to the closest cluster (lowest RTT).

Balancing connections across a system and within clusters has come up. We have added the ability for a system user to disconnect certain clients and we will build that up to a function in the NATS cli to auto re-balance a NATS system over a period of time.

[derekcollison]

nats server request kick -h
usage: nats server request kick <client> <server>

Disconnects a client immediately

Args:
  ID         The Client ID to disconnect
  SERVER_ID  The Server ID to disconnect the client from

Global Flags:
  -h, --help                    Show context-sensitive help
      --version                 Show application version.
  -s, --server=URL              NATS server urls ($NATS_URL)
      --user=USER               Username or Token ($NATS_USER)
      --password=PASSWORD       Password ($NATS_PASSWORD)
      --connection-name=NAME    Nickname to use for the underlying NATS Connection
      --creds=FILE              User credentials ($NATS_CREDS)
      --nkey=FILE               User NKEY ($NATS_NKEY)
      --tlscert=FILE            TLS public certificate ($NATS_CERT)
      --tlskey=FILE             TLS private key ($NATS_KEY)
      --tlsca=FILE              TLS certificate authority chain ($NATS_CA)
      --[no-]tlsfirst           Perform TLS handshake before expecting the server greeting
      --timeout=DURATION        Time to wait on responses from NATS ($NATS_TIMEOUT)
      --socks-proxy=PROXY       SOCKS5 proxy for connecting to NATS server ($NATS_SOCKS_PROXY)
      --js-api-prefix=PREFIX    Subject prefix for access to JetStream API
      --js-event-prefix=PREFIX  Subject prefix for access to JetStream Advisories
      --js-domain=DOMAIN        JetStream domain to access
      --inbox-prefix=PREFIX     Custom inbox prefix to use for inboxes
      --colors=SCHEME           Sets a color scheme to use ($NATS_COLOR)
      --context=NAME            Configuration context ($NATS_CONTEXT)
      --trace                   Trace API interactions
      --no-context              Disable the selected context
      --limit=2048              Limit the responses to a certain amount of records
      --offset=0                Start at a certain record
      --name=NAME               Limit to servers matching a server name
      --host=HOST               Limit to servers matching a server host name
      --cluster=CLUSTER         Limit to servers matching a cluster name
      --tags=TAGS ...           Limit to servers with these configured tags

[YanKawaYu]

Thanks! I will look into that. Looking forward to your auto re-balance function