-
Type:
Task
-
Resolution: Cannot Reproduce
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Connectivity
-
Labels:
hi
we have upgraded to 2.2.2 and even though we see the improvement, we still have connection timeout issues. here is the stacktrace:
Unhandled Exception: System.TimeoutException: A timeout occured after 30000ms selecting a server using CompositeServerSelector{ Selectors = ReadPreferenceServerSelector{ ReadPreference = { Mode = Primary, TagSets = [] } }, LatencyLimitingServerSelector { AllowedLatencyRange = 00:00:00.0150000 } }. Client view of cluster state is { ClusterId : "1", ConnectionMode : "Automatic", Type : "Unknown", State : "Disconnected", Servers : [{ ServerId: "{ ClusterId : 1, EndPoint : "Unspecified/host:port" }", EndPoint: "Unspecified/host/port", State: "Disconnected", Type: "Unknown" }] }. at MongoDB.Driver.Core.Clusters.Cluster.ThrowTimeoutException(IServerSelector selector, ClusterDescription description) at MongoDB.Driver.Core.Clusters.Cluster.WaitForDescriptionChangedHelper.HandleCompletedTask(Task completedTask) at MongoDB.Driver.Core.Clusters.Cluster.WaitForDescriptionChanged(IServerSelector selector, ClusterDescription description, Task descriptionChangedTask, TimeSpan timeout, CancellationToken cancellationToken) at MongoDB.Driver.Core.Clusters.Cluster.SelectServer(IServerSelector selector, CancellationToken cancellationToken) at MongoDB.Driver.MongoServer.Connect(TimeSpan timeout) at MongoDB.Driver.MongoServer.Connect()
here is what we add to connection string connecttimeout=300000;maxpoolsize=800;waitQueueSize=2000;waitQueueTimeout=5m.
- depends on
-
CSHARP-2147 Add logging of heartbeat information and SDAM state transitions
-
- Closed
-
- is related to
-
CSHARP-1515 Queries using the Legacy API can leak connections resulting in TimeoutExceptions
-
- Closed
-