-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: CMAP, Performance
-
Needed
-
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
- duplicates
-
JAVA-4288 Allow configuration of MAX_CONNECTING on the connection pool after 4.3.x changes
- Closed
- is depended on by
-
CSHARP-3885 [Unconfigurable] connection rate limiter in 2.13.x breaks existing applications
- Closed
- split to
-
RUST-1096 Make maxConnecting configurable
- Backlog
-
CDRIVER-4218 Make maxConnecting configurable
- Closed
-
CSHARP-3952 Make maxConnecting configurable
- Closed
-
CXX-2413 Make maxConnecting configurable
- Closed
-
GODRIVER-2219 Make maxConnecting configurable
- Closed
-
MOTOR-856 Make maxConnecting configurable
- Closed
-
NODE-3750 Make maxConnecting configurable
- Closed
-
PHPLIB-759 Make maxConnecting configurable
- Closed
-
PYTHON-3005 Make maxConnecting configurable
- Closed
-
RUBY-2840 Make maxConnecting configurable
- Closed
-
JAVA-4390 Make maxConnecting configurable
- Closed
- links to