Hello Gustavo,
We have the golang web-application for distribution a lot of traffic. Our data stored in mongodb with replicaset: arbiter, master and two slave. Throughput over 1000 requests per seconds. And we have some troubles with the connection to database
Sometimes we lose connection for one node, and by reconnection we lose many traffic. The connection breaking occurs with error like: read tcp 10.135.47.142:51520->
10.135.41.40:27017: i/o timeout or Closed explicitly. Why we lose connection? So if one node is not available, mgo must connect to another mongodb nodes without loss traffic? newSession.LiveServers() shows available nodes at the crash moment.
Can you help us, maybe the code need change?