chore(NODE-7418): skip csot change stream tests on sharded topology#4969
Open
tadjik1 wants to merge 1 commit into
Open
chore(NODE-7418): skip csot change stream tests on sharded topology#4969tadjik1 wants to merge 1 commit into
tadjik1 wants to merge 1 commit into
Conversation
On sharded clusters the initial $changeStream aggregate is sent with maxTimeMS set to the remaining CSOT budget. mongos propagates this value to each shard as maxAwaitTimeMS on the oplog cursor, causing the server to block for the full budget when no events are present. This makes all createChangeStream CSOT tests time out on sharded+SSL hosts. The legacy-timeout retryability tests (socketTimeoutMS=100) also fail because SSL connection establishment on the sharded+SSL Evergreen host exceeds 100ms after a socket timeout invalidates the first connection. Skip all affected tests on sharded topology until NODE-7418 lands.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the CSOT unified spec test runner wiring to skip a set of change stream–related CSOT tests when running against sharded topologies, addressing consistent failures/hangs on sharded environments while the underlying fix is tracked in NODE-7418.
Changes:
- Add a sharded-topology skip filter for a curated list of CSOT
createChangeStreamtest descriptions. - Add a second sharded-topology skip for the modified unified CSOT change stream test case (
unified-csot-node-specs).
| configuration.topologyType === 'Sharded' && | ||
| csotChangeStreamShardedSkips.has(test.description) | ||
| ) { | ||
| return 'TODO(NODE-7418): CSOT createChangeStream tests hang on sharded clusters, fixed by NODE-7418'; |
| configuration.topologyType === 'Sharded' && | ||
| test.description === 'timeoutMS is refreshed for getMore if maxAwaitTimeMS is set' | ||
| ) { | ||
| return 'TODO(NODE-7418): CSOT createChangeStream tests hang on sharded clusters, fixed by NODE-7418'; |
johnmtll
reviewed
Jun 23, 2026
| // TODO(NODE-7418): same root cause as csotChangeStreamShardedSkips above. | ||
| if ( | ||
| configuration.topologyType === 'Sharded' && | ||
| test.description === 'timeoutMS is refreshed for getMore if maxAwaitTimeMS is set' |
Contributor
There was a problem hiding this comment.
'timeoutMS is refreshed for getMore if maxAwaitTimeMS is set' is already present above in skippedTests. It may already be skipped entirely.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Summary of Changes
Skips 14 CSOT change stream tests that consistently fail on sharded+SSL topology.
The proper fix is tracked in NODE-7418 and is in progress in #4872.
Double check the following
npm run check:lint)type(NODE-xxxx)[!]: description