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

ConnectionPool getConnection may shorten specified connection timeout

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor - P4
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Service Arch
    • ALL
    • Hide

      1. Remove ConnectionPool shortening timeout.
      2. Trigger an evergreen build (here is a recent one)
      3. Analyze crashes for ConnectionPoolTest::SetupTimeoutsDontTimeoutUnrelatedRequests

      Show
      1. Remove ConnectionPool shortening timeout. 2. Trigger an evergreen build ( here is a recent one) 3. Analyze crashes for ConnectionPoolTest::SetupTimeoutsDontTimeoutUnrelatedRequests
    • 2

    Description

      ConnectionPool::getConnection accepts one parameter to set how many milliseconds a connection can take, however the logic within may shorten the timeout to the controller's pending timeout.

      During multiple discussion it isn't clear if this is still needed and why, removing it causes few ConnectionPool executor_tests fail.

      amirsaman.memaripour@mongodb.com also brought up the point that it doesn't make much of a difference when this method, which is purely responsible for acquiring a connection to its peer, take longer than 20 seconds.

      The acceptance criteria for this ticket is to define if ConnectionPool should interfere with its given timeout, and if not, remove it.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-servicearch Backlog - Service Architecture
              daniel.morilha@mongodb.com Daniel Morilha (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: