Background task should clean up perished connections even when minPoolSize = 0

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 3
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a... user with an unset minPoolSize and set maxIdleTimeMS
      I want... perished connections to be periodically cleaned up in the background
      So that...  I don't leave unusable resources open while the pool is idle

      User Experience

      Unknowns

      • Should we update the background thread frequency to be configurable?

      Acceptance Criteria

      Implementation Requirements

      Testing Requirements

      • Add a test to make sure that the cleanup happens (make sure it fails before the fix and succeeds after)

      Documentation Requirements

      • Update API docs for maxIdleTimeMS to reflect spec documentation and also clarify the difference between being 'idle' / or unused and being marked as 'idle'

      Follow Up Requirements

      • N/A

            Assignee:
            Bailey Pearson
            Reporter:
            Aditi Khare (Inactive)
            Durran Jordan
            Votes:
            4 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: