-
Type: Spec Change
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: CMAP, Load Balancer
-
Needed
-
Summary
The CMAP spec currently requires that pools are marked as paused after being cleared, regardless of whether the pool is associated with a load balancer or not. The benefits of pausing the pool / clearing the WaitQueue aren't present when the endpoint is a load balancer though, so we should update the spec wording accordingly.
Motivation
Who is the affected end user?
Driver authors, potentially users depending on drivers' implementations.
How does this affect the end user?
Unclear, depends on drivers' implementations.
How likely is it that this problem or use case will occur?
Unclear, depends on drivers' implementations.
If the problem does occur, what are the consequences and how severe are they?
Unclear, depends on drivers' implementations.
Is this issue urgent?
It will help drivers implement DRIVERS-781 and avoid potential bugs.
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
No
- causes
-
DRIVERS-2236 CMAP inconsistency when clearing load balanced pools
- Closed
- split to
-
PYTHON-2933 Clarify clearing behavior for load balanced pools
- Backlog
-
CDRIVER-4180 Clarify clearing behavior for load balanced pools
- Backlog
-
CXX-2384 Clarify clearing behavior for load balanced pools
- Backlog
-
NODE-3657 Clarify clearing behavior for load balanced pools
- Closed
-
CSHARP-3892 Clarify clearing behavior for load balanced pools
- Closed
-
GODRIVER-2177 Clarify clearing behavior for load balanced pools
- Closed
-
JAVA-4332 Clarify clearing behavior for load balanced pools
- Closed
-
MOTOR-828 Clarify clearing behavior for load balanced pools
- Closed
-
PHPLIB-731 Clarify clearing behavior for load balanced pools
- Closed
-
RUBY-2804 Clarify clearing behavior for load balanced pools
- Closed
-
RUST-1043 Clarify clearing behavior for load balanced pools
- Closed