Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-2423

WaitQueueTimeoutError reports pinned connections when no pinning occurs

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 1.12.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Scope

      • Do not include the "connections in use by cursors: x, connections in use by transactions: y, connections in use by other operations: z" part of the WaitQueueTimeoutError when connections are not being pinned.

      Background & Motivation

      When connected to a Load Balancers, drivers are required to pin connections to cursors and transactions.
      Drivers are required to report the pinned connections in the WaitQueueTimeoutError.

      The Go driver always reports pinned connections in WaitQueueTimeoutError, even if no connection pinning occurs.

      That can cause confusing error messages when not connected to a load balanced cluster. Example:

      timed out while checking out a connection from connection pool: context canceled; maxPoolSize: 300, connections in use by cursors: 0, connections in use by transactions: 0, connections in use by other operations: 0

            Assignee:
            qingyang.hu@mongodb.com Qingyang Hu
            Reporter:
            kevin.albertson@mongodb.com Kevin Albertson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: