[CSHARP-2631] Several MongoConnectionException's per hour in production backend logs Created: 11/Jun/19 Updated: 25/Jun/20 Resolved: 25/Jun/20 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | 2.7.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Timofey Myagkikh | Assignee: | Wan Bachtiar |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Azure, VM Windows Server Datacenter 2019, Net Core Runtime 2.2.3.27414 |
||
| Attachments: |
|
| Case: | (copied to CRM) |
| Description |
|
Hello! In production backend logs I see permanent exceptions (around 10 per hour) like this: ``` If I correctly understood, for clients this exception looks like 500 http error. In atlas replica set logs, nothing like MongoConnectionException's or any other connection problem. Could you describe this behavior of mongodb C# driver and suggest a workaround for these situations? If you need any metrics, I could share atlas monitoring charts or something else if you need it. |
| Comments |
| Comment by Rachelle Palmer [ 25/Jun/20 ] |
|
Hi there, thank you for reaching out to MongoDB. As this sounds more like a support issue, I wanted to give you some resources to get this question answered more quickly:
Thank you! |
| Comment by Timofey Myagkikh [ 13/Jun/19 ] |
|
This is my wireshark dump.
|