-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: 1.8.1
-
Component/s: None
A Disconnected Primary MongoServerInstance ServerInformation is never resetted and though the MongoServer.Primary is never Single()
The Issue is in MongoServerInstance.cs a lot of your actions start with a Ping() => Ping(MongoConnection connection) => in case of an Exception it throws and though the State is Never resetted.
- is duplicated by
-
CSHARP-755 MongoServer.Primary is not thread-safe when using a replicaset
- Closed
- is related to
-
CSHARP-722 Provide a method to inspect the state of a cluster
- Closed