Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DRIVERS-2969: increase CSOT timeouts for session prose tests #1643

Merged
merged 3 commits into from
Sep 4, 2024
Merged

DRIVERS-2969: increase CSOT timeouts for session prose tests #1643

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a64e7a5
DRIVERS-2969: increase CSOT timeouts for session prose tests
nbbeeken Aug 29, 2024
dcce326
chore: bump gridFS times and mention using one mongos
nbbeeken Sep 3, 2024
cca2ca7
fix: lint
nbbeeken Sep 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 17 additions & 13 deletions source/client-side-operations-timeout/tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -314,7 +314,9 @@ error occurs.

### 6. GridFS - Upload

Tests in this section MUST only be run against server versions 4.4 and higher.
Tests in this section MUST only be run against server versions 4.4 and higher. Drivers SHOULD apply
[useMultipleMongoses=false](../../unified-test-format/unified-test-format.md#entity) as described in the unified test
format when testing on sharded clusters to ensure failpoint are hit by only using one mongos.

#### uploads via openUploadStream can be timed out

Expand All @@ -329,12 +331,12 @@ Tests in this section MUST only be run against server versions 4.4 and higher.
data: {
failCommands: ["insert"],
blockConnection: true,
blockTimeMS: 15
blockTimeMS: 200
}
}
```

3. Create a new MongoClient (referred to as `client`) with `timeoutMS=10`.
3. Create a new MongoClient (referred to as `client`) with `timeoutMS=150`.

4. Using `client`, create a GridFS bucket (referred to as `bucket`) that wraps the `db` database.

Expand Down Expand Up @@ -364,12 +366,12 @@ This test only applies to drivers that provide an API to abort a GridFS upload s
data: {
failCommands: ["delete"],
blockConnection: true,
blockTimeMS: 15
blockTimeMS: 200
}
}
```

3. Create a new MongoClient (referred to as `client`) with `timeoutMS=10`.
3. Create a new MongoClient (referred to as `client`) with `timeoutMS=150`.

4. Using `client`, create a GridFS bucket (referred to as `bucket`) that wraps the `db` database with
`chunkSizeBytes=2`.
Expand All @@ -387,7 +389,9 @@ This test only applies to drivers that provide an API to abort a GridFS upload s

### 7. GridFS - Download

This test MUST only be run against server versions 4.4 and higher.
This test MUST only be run against server versions 4.4 and higher. Drivers SHOULD apply
[useMultipleMongoses=false](../../unified-test-format/unified-test-format.md#entity) as described in the unified test
format when testing on sharded clusters to ensure failpoint are hit by only using one mongos.

1. Using `internalClient`, drop and re-create the `db.fs.files` and `db.fs.chunks` collections.

Expand All @@ -411,7 +415,7 @@ This test MUST only be run against server versions 4.4 and higher.
}
```

3. Create a new MongoClient (referred to as `client`) with `timeoutMS=10`.
3. Create a new MongoClient (referred to as `client`) with `timeoutMS=150`.

4. Using `client`, create a GridFS bucket (referred to as `bucket`) that wraps the `db` database.

Expand All @@ -429,7 +433,7 @@ This test MUST only be run against server versions 4.4 and higher.
data: {
failCommands: ["find"],
blockConnection: true,
blockTimeMS: 15
blockTimeMS: 200
}
}
```
Expand Down Expand Up @@ -524,7 +528,7 @@ and password).
This test MUST only be run against replica sets and sharded clusters with server version 4.4 or higher. It MUST be run
three times: once with the timeout specified via the MongoClient `timeoutMS` option, once with the timeout specified via
the ClientSession `defaultTimeoutMS` option, and once more with the timeout specified via the `timeoutMS` option for the
`endSession` operation. In all cases, the timeout MUST be set to 10 milliseconds.
`endSession` operation. In all cases, the timeout MUST be set to 150 milliseconds.

1. Using `internalClient`, drop the `db.coll` collection.

Expand All @@ -537,7 +541,7 @@ the ClientSession `defaultTimeoutMS` option, and once more with the timeout spec
data: {
failCommands: ["abortTransaction"],
blockConnection: true,
blockTimeMS: 15
blockTimeMS: 200
}
}
```
Expand All @@ -555,7 +559,7 @@ the ClientSession `defaultTimeoutMS` option, and once more with the timeout spec

5. Using `session`, execute `session.end_session`

- Expect this to fail with a timeout error after no more than 15ms.
- Expect this to fail with a timeout error after no more than 150ms.

### 10. Convenient Transactions

Expand All @@ -574,12 +578,12 @@ Tests in this section MUST only run against replica sets and sharded clusters wi
data: {
failCommands: ["insert", "abortTransaction"],
blockConnection: true,
blockTimeMS: 15
blockTimeMS: 200
}
}
```

3. Create a new MongoClient (referred to as `client`) configured with `timeoutMS=10` and an explicit ClientSession
3. Create a new MongoClient (referred to as `client`) configured with `timeoutMS=150` and an explicit ClientSession
derived from that MongoClient (referred to as `session`).

4. Using `session`, execute a `withTransaction` operation with the following callback:
Expand Down
Loading