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

Handle exceeded time limit in NI connection hook

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.1, 3.5.1
    • Component/s: Networking
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4, v3.2
    • Sprint:
      Platforms 2017-01-23
    • Linked BF Score:
      0

      Description

      max_time_ms_sharded.js uses a fail point to trigger immediate ExceededTimeLimit returns from commands. This triggers during connection establishment via the connection hook, which returns ExceededTimeLimit to the connection pool and causes us to spin on connection creation.

      The fix involves checking for ExceededTimeLimit returns and converting them to CommandFailed to avoid the spinning.

        Attachments

          Activity

            People

            Assignee:
            jason.carey Jason Carey
            Reporter:
            jason.carey Jason Carey
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: