Socket leak in copy_database

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Blocker - P1
    • 0.3.2
    • Affects Version/s: 0.2, 0.3, 0.2.1, 0.3.1
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Motor leaks one socket in each call to copy_database.

      The socket is closed by garbage collection, but it continues to count toward max_pool_size. If max_pool_size is finite (the default is 100) then the client hangs after max_pool_size calls to copy_database.

      Applies to MotorClient and MotorReplicaSetClient.

      Motor users apparently don't call copy_database much, or this would have been reported earlier.

              Assignee:
              A. Jesse Jiryu Davis
              Reporter:
              A. Jesse Jiryu Davis
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: