Make ConnectionPool::SpecificPool::updateEventTimer topology reconfiguration aware

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Daniel Morilha (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: