[CSHARP-2540] A timeout occured after 30000ms selecting a server using CompositeServerSelector{ Selectors = MongoDB.Driver.MongoClient+AreSessionsSupportedServerSelector, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00.0150000 } } Created: 07/Mar/19 Updated: 08/Mar/23 Resolved: 11/Mar/19 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | 2.7.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | santhosh K | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Azure |
||
| Issue Links: |
|
||||||||
| Description |
|
Hi, I have a docker containerized .Net core web API application running in AKS which connects to Azure cosmos db using Mondb .net driver to perform CRUD operations. I don't face any issues running locally, but in the AKS cluster MongoDB client throws System.TimeoutException frequently and it gets resolved only after restarting the Pod. MongoDb .Net driver Version: 2.7.3(latest) MongoClient is registered as a singleton service and enabled Ssl as well. Please find the exception below and let me know how to resolve this as early as possible. Its creating issues and am unable to predict the root cause as it occurs only in the azure cluster. Suggest any workarounds if possible. Thanks in advance!
|
| Comments |
| Comment by James Kovacs [ 08/Mar/23 ] |
|
For more information, see Why Does the Driver Throw a Timeout During Server Selection? in the MongoDB .NET/C# Driver FAQ. |
| Comment by Ian Whalen (Inactive) [ 11/Mar/19 ] |
|
dupe of |