-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 2.5
-
Component/s: Connectivity
-
None
We occasionally get JIRA issues reporting suspicious connectivity issues. The errors look like connectivity issues but the reporters sometimes state that the server and network were healthy and that there should not have been any connectivity issues.
It would be helpful to log the heartbeat information and the SDAM state transitions to provide more visibility into exactly what is happening.
- is depended on by
-
CSHARP-1538 Legacy Driver Connect() times out.
- Closed
- is related to
-
CSHARP-1752 Driver never recovers connection to replica set
- Closed
-
CSHARP-1855 Upgrading from Mongo Legacy 1.11.0 to 2.4.0 (or 2.3.0) connection Timeout Issues
- Closed
-
CSHARP-1663 MongoDB.Driver.Core.Clusters.Cluster.ThrowTimeoutException
- Closed
-
CSHARP-2580 Add reference docs for SDAM logging
- Closed