[SERVER-64773] "codeName": "NetworkInterfaceExceededTimeLimit", "errmsg": "Couldn't get a connection within the time limit Created: 22/Mar/22 Updated: 22/Jun/22 Resolved: 12/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Debalina Saha | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Below issue we faced where VMs were accessible. But Mongodb connection was failing and no application was able to connect during that duration. We had to restart one of the VM shard. Though the issue resolved after an hour , we need to find RCA on this. After checking we found this "NetworkInterfaceExceededTimeLimit" error in mongos log, which I believe has been taken cared in Mongo 4.0 version. 1.Error message received in application: B. 2.Error message in Mongos logs: { , } =================================================== |
| Comments |
| Comment by Eric Sedor [ 29/Mar/22 ] |
|
Hi debalina.saha@accenture.com, I can imagine a few expected causes of this. For this issue we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project. Thank you! |