[DRIVERS-1948] Add a CMAP test that verifies the background thread hands over connections to threads doing checkout Created: 13/Oct/21  Updated: 29/Apr/22

Status: Implementing
Project: Drivers
Component/s: CMAP
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Valentin Kavalenka Assignee: Valentin Kavalenka
Resolution: Unresolved Votes: 0
Labels: size-small, spec-change, yaml-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CSHARP-3901 Add a CMAP test that verifies the bac... Backlog
split to GODRIVER-2182 Add a CMAP test that verifies the bac... Backlog
split to RUST-1052 Add a CMAP test that verifies the bac... Backlog
split to CDRIVER-4186 Add a CMAP test that verifies the bac... Closed
split to CXX-2386 Add a CMAP test that verifies the bac... Closed
split to JAVA-4346 Add a CMAP test that verifies the bac... Closed
split to NODE-3666 Add a CMAP test that verifies the bac... Closed
split to PHPLIB-732 Add a CMAP test that verifies the bac... Closed
split to PYTHON-2941 Add a CMAP test that verifies the bac... Closed
split to RUBY-2808 Add a CMAP test that verifies the bac... Closed
split to MOTOR-829 Add a CMAP test that verifies the bac... Closed
Problem/Incident
is caused by JAVA-4316 The background thread should be able ... Closed
Driver Changes: Needed
Downstream Changes Summary:

Implement the CMAP specification change done in https://github.com/mongodb/specifications/pull/1078. The PR also introduced a test that verifies the implementation.

Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4186 Won't Do
CXX-2386 Won't Do
CSHARP-3901 Backlog
GODRIVER-2182 Backlog
JAVA-4346 Fixed 4.3.4
NODE-3666 Done
PHPLIB-732 Won't Fix
PYTHON-2941 Fixed 4.0
MOTOR-829 Duplicate
RUBY-2808 Duplicate
RUST-1052 Backlog
SWIFT-1369 Duplicate

 Description   

Summary

What is the problem or use case, what are we trying to achieve?
Make sure the driver does not have increased connection checkout latencies during temporary states when a pool is not populated to its min size.

Motivation

Who is the affected end user?

A user of a driver.

How does this affect the end user?

If a driver does not behave the way the test expects, it's a performance bug that may affect driver users. JAVA-4316 is an example of a situation when the user is affected by this bug in the Java driver.

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

Not very likely, and if there is a problem with connection checkout latencies, the behavior expected by the test is unlikely to solve the problem in full.

If the problem does occur, what are the consequences and how severe are they?

May cause higher checkout latencies during temporary states when a pool is not populated to its min size.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Depends on whether a driver has the specific performance bug or not. If not, then the driver will only need to grab the new test scenario.



 Comments   
Comment by Githook User [ 05/Nov/21 ]

Author:

{'name': 'Valentin Kovalenko', 'email': 'valentin.kovalenko@mongodb.com', 'username': 'stIncMale'}

Message: Add a CMAP test that verifies the background thread hands over connections to threads doing checkout (#1078)

DRIVERS-1948
Branch: master
https://github.com/mongodb/specifications/commit/ec4fae839563617dc27ff8e793f9494f64d2a5a3

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