Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-1943

Make maxConnecting configurable

    XMLWordPrintable

Details

    • Improvement
    • Status: Implementing
    • Unknown
    • Resolution: Unresolved
    • CMAP
    • Needed
    • Hide

      Implement the new maxConnecting connection pool and connection string option as specified in this commit.

      Show
      Implement the new maxConnecting connection pool and connection string option as specified in this commit .

    Description

      Summary

      The CMAP spec currently requires setting maxConnecting to 2. There are some user scenarios where this setting is not optimal, and degrades application performance.

      Consider allowing users to configure maxConnecting setting.
      Drivers should also provide documentation suggesting the default value of 2 (or other) for minimizing the risk of connection storms.

      Motivation

      Who is the affected end user?

      Customers with workloads for which maxConnecting=2 causes degraded performance (see linked tickets).

      How does this affect the end user?

      Some users experience performance degradation, which is supposed to be addressed by this setting.

      How likely is it that this problem or use case will occur?

      Unclear, probably an edge case.

      If the problem does occur, what are the consequences and how severe are they?

      Degraded performance

      Is this issue urgent?

      This prevents some users from upgrading to the latest driver.

      Is this ticket required by a downstream team?

      No

      Is this ticket only for tests?

      No

      Attachments

        Issue Links

          Activity

            People

              valentin.kovalenko@mongodb.com Valentin Kavalenka
              boris.dogadov@mongodb.com Boris Dogadov
              Votes:
              3 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated: