first, congrats for the work achieved on Aerospike, it’s an amazing tech and we are pretty happy with it.
We are using Aerospike for more than a year now, without issues.
Since we updated the Go client library to its last version we got more and more i/o timeout errors:
read tcp 10.0.0.x:56026->w.x.y.z:3000: i/o timeout
First I increased the timeouts and retries configuration of the Go client:
client.DefaultWritePolicy.SocketTimeout = 30*time.Second
client.DefaultWritePolicy.MaxRetries = 1000
client.DefaultWritePolicy.Timeout = 30*time.Second
client.DefaultPolicy.SocketTimeout = 30*time.Second
client.DefaultPolicy.MaxRetries = 1000
client.DefaultPolicy.Timeout = 30*time.Second
I was able to get rid of most of the timeouts with this configuration, but it still seems to happen sometimes. I am on a pretty good internet connexion within the US to an amazon ec2 instance located in Virginia, so I don’t understand where is the weak point here. I also deployed the very last version of Aerospike v4.3.12 but it didn’t fix the issue.
Do you know how can I configure the new Aerospike Go client in order to make it more resilient ?
Let me know, best, Romain.