[SERVER-46866] NetworkInterfaceExceededTimeLimit 'timeout' in logs is misleading Created: 13/Mar/20 Updated: 03/Aug/23 Resolved: 17/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The timeout that ends up being logged is not the timeout of the request (ie, the total time request spent) but it appears to be the time in between the last time ConnectionPool::SpecificPool::updateEventTimer was called and the request with the earliest expiration. |
| Comments |
| Comment by Amirsaman Memaripour [ 17/Jun/20 ] |
|
|