Summary

What is the problem or use case, what are we trying to achieve?

When a driver works in load-balanced (LB) mode, there is no server selection happening in the driver. The server selection spec does not explicitly say anything regarding the server selection in LB mode, however, it has logging/load-balanced.json test, that expects "Server selection started"/"Server selection succeeded" log messages in LB mode.

We should consider removing server selection logs in LB mode and the test that requires that logging. If we decide to leave the logs, then we should explain in the server selection spec the reasoning behind the requirement to have them.

Motivation

It does not seem useful to maintain the code and tests for server selection logs in LB mode given that there is no server selection in LB mode.

Who is the affected end user?

Who are the stakeholders?

The maintainers of the drivers.

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

A user won't see server selection log messages when using a driver in LB mode, which is fine, given that there is no server selection involved.

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

Main path? Edge case?

N/A

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?

This is likely a minor annoyance.

Is this issue urgent?

Does this ticket have a required timeline? What is it?

No.

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

No.

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?

No.

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?

The requirement is either removed or explained it in the spec.