Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-46866

NetworkInterfaceExceededTimeLimit 'timeout' in logs is misleading

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Service Arch
    • ALL

      https://github.com/mongodb/mongo/blob/f3a8b79683137be0f8256358a4d424fa88ebfda7/src/mongo/executor/connection_pool.cpp#L1115

      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.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: