Details
-
Bug
-
Resolution: Gone away
-
Major - P3
-
None
-
1.3.4
-
None
-
Go 1.14.3
MongoDB 3.0.11
Linux
Description
I started to receive this error in several of my applications:
server selection error: server selection timeout, current topology: { Type: ReplicaSetNoPrimary, Servers: [{ Addr: server-3:27506, Type: RSPrimary, State: Connected, Average RTT: 4820465 }, { Addr: server-1:27506, Type: RSSecondary, State: Connected, Average RTT: 4725379 }, { Addr: server-2:27506, Type: RSSecondary, State: Connected, Average RTT: 4543115 }, { Addr: arbiter-2.sendinblue.com:27506, Type: RSArbiter, State: Connected, Average RTT: 589930 }, { Addr: arbiter-1.sendinblue.com:27506, Type: RSArbiter, State: Connected, Average RTT: 4579950 }, ] } |
All MongoDB queries returned the same error.
In order to fix the issue, I had to restart my application (and create a new Client object).
I guess there is a "broken" connection in the pool, and it is still used even if it's not working anymore ?
This is a MongoDB 3.0.11 cluster.