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

Investigate negative timeouts in connection pool

    XMLWordPrintable

    Details

    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Service Arch 2021-07-12, Service Arch 2021-08-09, Service Arch 2021-08-23, Service Arch 2021-10-04, Service Arch Test, Top Priority Tickets
    • Story Points:
      3

      Description

      Connection pools setup event timers to check if the network interface time limit is exceeded. Timeouts are handled by fulfilling the promise for pending requests with ErrorCodes::NetworkInterfaceExceededTimeLimit. Older versions (v4.4 and before) also include the timeout (in milliseconds) in the error description.

      The timeout calculations may be susceptible to underflow, where the calculated timeout could be a negative number. This ticket should investigate the possibility of negative timeouts in ConnectionPool::SpecificPool::updateEventTimer() and propose fixes if necessary.

       

      Acceptance criteria:

      Write unit tests for the above mentioned function. Ensure one of the triggers a negative timeout and fix it. Timebox it to 1 day to write the unit test. 

        Attachments

          Activity

            People

            Assignee:
            tyler.seip Tyler Seip
            Reporter:
            amirsaman.memaripour Amirsaman Memaripour
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated: