[SERVER-46978] Re-starting a secondary database in a replica set generates NetworkInterfaceExceededTimeLimit errors Created: 19/Mar/20 Updated: 19/Mar/20 Resolved: 19/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Ian Hannah | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Please see We have carried out extensive tests and we are ONLY getting these network errors once the secondary gets behind and not before. |
| Comments |
| Comment by Kelsey Schubert [ 19/Mar/20 ] |
|
Thanks for the additional information. Unfortunately, as Dima explained, we can not effectively investigate this issue on the SERVER project. At this time, there isn't a clear indication of a bug in MongoDB. Therefore, we suggest reaching out for help on the MongoDB Community Forums or on Stack Overflow with the mongodb tag. If you would like a more in depth investigation, including review of your configuration settings and specific recommendations which may address this issue, please look into Enterprise-Grade Support. Thank you, |