[DRIVERS-1938] mongos pinning is conflated with connection pinning in operations Created: 01/Oct/21  Updated: 27/Oct/23  Resolved: 14/Oct/21

Status: Closed
Project: Drivers
Component/s: Unified Test Runner
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Kaitlin Mahar Assignee: Kaitlin Mahar
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Driver Changes: Not Needed

 Description   

Currently assertSessionPinned / assertSessionUnpinned in the spec state:

The assertSessionPinned operation instructs the test runner to assert that the given session is pinned to a mongos server.

The assertSessionUnpinned operation instructs the test runner to assert that the given session is not pinned to a mongos server.

Similarly, targetedFailPoint's wording is currently specific to mongoses:

The targetedFailPoint operation instructs the test runner to configure a fail point on a specific mongos.

Some of the transactions tests which we are expected to run against serverless (for example, this one) use these operations, even though no mongoses exist and what is really technically required to be pinned is a connection - and therefore implicitly a (non-mongos) host which the connection is to, though maybe many drivers end up pinning the host explicitly as an implementation detail.

It seems like we may want to clarify the wording on these operations to cover the difference in expectation across topologies.



 Comments   
Comment by Kaitlin Mahar [ 14/Oct/21 ]

as it turns out, the tests I was referring to are not supposed to be run against load balanced clusters at all. so the language in the unified test runner spec is correct and these assertions only come up in the context of testing against sharded clusters where mongoses are present. no work to do here.

Generated at Thu Feb 08 08:24:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.