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

Connection leak caused by connection-to-transaction pinning when connected to a load balancer

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 1.12.1, 1.11.8, 1.11.9
    • 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?

      In a Live migration, the Mongosync kept crashing because the connection pool is empty. After we added pool monitoring, we found the pinned connection to transactions kept increasing and never decreases. After talking with matt.dale@mongodb.com , we think there could be a potential driver bug that caused the connection never get released when the client is connected with a load balancer unless that session is used to run another transaction or other non-transaction operation.

      Please prioritize the fix because live migration would be potentially blocked by this bug. 

            Assignee:
            matt.dale@mongodb.com Matt Dale
            Reporter:
            huan.li@mongodb.com Huan Li (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: