-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: 1.0.3
-
Component/s: Connections
-
None
My daemon process stopped working unexpectedly.
Here is the error message returned by the MongoDB driver.
server selection error: server selection timeout current topology: Type: ReplicaSetNoPrimary Servers: Addr: archive6-3.xxx.com:27506, Type: RSPrimary, State: Connected, Average RTT: 5002238 Addr: archive6-1.xxx.com:27506, Type: RSSecondary, State: Connected, Average RTT: 4990684 Addr: archive6-2.xxx.com:27506, Type: RSSecondary, State: Connected, Average RTT: 5050808 Addr: archive6-arb1.xxx.com:27506, Type: RSArbiter, State: Connected, Average RTT: 4962164 Addr: archive6-arb2.xxx.com:27506, Type: RSArbiter, State: Connected, Average RTT: 848065
The MongoDB client object is no more usable: all MongoDB queries fail with this error.
The only solution is to restart my process, which creates a new client.
I don't understand what is the problem:
- the driver reports that there is no primary
- all nodes are in "connected" state
- when I check manually with rs.status(), everything is fine
Is it possible that the Go MongoDB driver is in a "corrupted" state ?