After upgrading from 1.11.0 to 2.4.0 or 2.3.0 C# legacy driver, we have connection issues being reported at random. The main modified code was dealing with how to connect to mongo. We changed it from:

db = new MongoClient(url).GetServer().GetDatabase(url.DatabaseName, settings);

to this:

db = new MongoServer(serverSettings).GetDatabase(url.DatabaseName, settings);

Any advice would be appreciated.

{"Type":"System.TimeoutException","Message":"A timeout occured after 30000ms selecting a server using CompositeServerSelector{ Selectors = WritableServerSelector, LatencyLimitingServerSelector

{ AllowedLatencyRange = 00:00:00.0150000 }

}. Client view of cluster state is { ClusterId : \"2\", ConnectionMode : \"ReplicaSet\", Type : \"ReplicaSet\", State : \"Disconnected\", Servers : [{ ServerId: \"

{ ClusterId : 2, EndPoint : \"Unspecified/aga-rogue-mongo01.aga-dev.sandbox.farm:27017\" }

\", EndPoint: \"Unspecified/aga-rogue-mongo01.aga-dev.sandbox.farm:27017\", State: \"Disconnected\", Type: \"Unknown\" }, { ServerId: \"

{ ClusterId : 2, EndPoint : \"Unspecified/aga-rogue-mongo02.aga-dev.sandbox.farm:27017\" }

\", EndPoint: \"Unspecified/aga-rogue-mongo02.aga-dev.sandbox.farm:27017\", State: \"Disconnected\", Type: \"Unknown\" }] }.","Source":"MongoDB.Driver.Core","Data":{},"StackTrace":" at MongoDB.Driver.Core.Clusters.Cluster.WaitForDescriptionChangedHelper.HandleCompletedTask(Task completedTask)\r\n at MongoDB.Driver.Core.Clusters.Cluster.WaitForDescriptionChanged(IServerSelector selector, ClusterDescription description, Task descriptionChangedTask, TimeSpan timeout, CancellationToken cancellationToken)\r\n at MongoDB.Driver.Core.Clusters.Cluster.SelectServer(IServerSelector selector, CancellationToken cancellationToken)\r\n at MongoDB.Driver.Core.Bindings.WritableServerBinding.GetReadChannelSource(CancellationToken cancellationToken)\r\n at MongoDB.Driver.Core.Operations.FindOperation`1.Execute(IReadBinding binding, CancellationToken cancellationToken)