Aerospike-go-cilent: high latency and connections stuck at CLOSE_WAIT

I am trying to start a server written in Golang that internally calls an aerospace client.

Initially, after the server startup delay, measured from the client side of the Aerosip, were under control, but after a while the delays became high and did not decrease.

Based on my observation during high latency, many connections from the aerospace client to the aerospace server are in the state close_wait

I am using the default settings for the ie client policy, ConnectionQueueSize = 256

andLimitConnectionsToQueueSize = true

My guess is that many connections are in a state close_wait

and we are limiting the connections that are waiting for a connection to close and create a new one, and due to the latency being high

If this is correct, how can we quickly close connections that are in a state close_wait

? Otherwise, what could be the reason for this?

PS,

  • We measured the latency from the aerospin server, it was less than 1ms (as expected)
  • No network congestion from the aerospace server side as well as the aerospace client side.
+3


source to share


1 answer


Limit the number of clients, which is one of the recommendations in the Go client overview , and definitely don't close connections quickly.



0


source







All Articles