-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Component/s: Load Balancer
-
Labels:None
-
Needed
Summary
Remove isMaster from the load balancer tests since drivers should never use it there per handshake specifications
If a server API version is requested or loadBalanced: True, drivers MUST use the hello command for the initial handshake and use the OP_MSG protocol.
What is the problem or use case, what are we trying to achieve?
Motivation
Who is the affected end user?
Who are the stakeholders?
How does this affect the end user?
Are they blocked? Are they annoyed? Are they confused?
How likely is it that this problem or use case will occur?
Main path? Edge case?
If the problem does occur, what are the consequences and how severe are they?
Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?
Is this issue urgent?
Does this ticket have a required timeline? What is it?
Is this ticket required by a downstream team?
Needed by e.g. Atlas, Shell, Compass?
Is this ticket only for tests?
This is just test improvements.
Acceptance Criteria
Investigate the following uses of fail commands in spec tests, and remove isMaster from load-balanced cases:
Mixes-topology cases:
- https://github.com/mongodb/specifications/blob/5786a46a59cdfeebab36edf6672cdf6f23dd636c/source/transactions/tests/legacy/mongos-recovery-token.yml#L213
- https://github.com/mongodb/specifications/blob/5786a46a59cdfeebab36edf6672cdf6f23dd636c/source/connection-monitoring-and-pooling/tests/cmap-format/pool-checkout-maxConnecting-is-enforced.yml#L13
- https://github.com/mongodb/specifications/blob/5786a46a59cdfeebab36edf6672cdf6f23dd636c/source/connection-monitoring-and-pooling/tests/cmap-format/pool-checkout-custom-maxConnecting-is-enforced.yml#L11
- https://github.com/mongodb/specifications/blob/5786a46a59cdfeebab36edf6672cdf6f23dd636c/source/connection-monitoring-and-pooling/tests/cmap-format/pool-create-min-size-error.yml#L13
load-balanced topology:
- related to
-
-
- Closed
-