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

Make ConnectionPool::SpecificPool::updateEventTimer topology reconfiguration aware

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • Service Arch
    • ALL
    • 0

    Description

      BF-20554 surfaced a problem where ConnectionPool::SpecificPool::updateEventTimer might incorrectly trigger deferredStateUpdateFunc while a topology reconfiguration is happening in the shard leading to client's DoS.

      The logic might have to consider when a topology reconfiguration happens and act appropriately.

      AC: After exceeding kHostRetryTimeout (currently hardcoded to 1 second), log how long it takes for getting a connection within the time limit before raising ErrorCodes::NetworkInterfaceExceededTimeLimit

      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:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: