Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
NODE-6547Backlog
Flaky: CSOT spec tests - socketTimeoutMS is ignored if timeoutMS is set - MongoNetworkTimeoutError [28]
https://spruce.mongodb.com/task/mongo_node_driver_next_windows_vsCurrent_large_gallium_test_4.2_replica_set_1965ed51296bac9149ecb077b6cafd43150a3a07_24_11_11_17_53_39/logs?execution=0&sortBy=STATUS&sortDir=ASC
Components
Flaky Test
NODE-6787Backlog
Flaky: CSOT spec test Non-tailable cursor lifetime [5]
https://spruce.mongodb.com/task/mongo_node_driver_next_rhel80_large_Node20_test_latest_load_balanced_196e08e9c2a61557bb95d956aa389ff1457c77ea_25_02_26_14_40_06/logs?execution=0&sortBy=STATUS&sortDir=ASC
Components
Flaky Test
NODE-6576Backlog
Flaky: timeoutMS applied to entire download, not individual parts [10]
Flaky test: timeoutMS applied to entire download, not individual parts
https://spruce.mongodb.com/task/mongo_node_driver_next_macos_1100_test_rapid_server_1673748b7572c01605eb123c873d1d0f324c0dda_24_11_21_20_00_45/logs?execution=0&sortBy=STATUS&sortDir=ASC
Components
Flaky Test
Affected Versions
6.10.0
SERVER-138135ClosedDone
Merge main-staging-poc branch 2026.10.27
Includes:
* [SERVER-136935|https://jira.mongodb.org/browse/SERVER-136935] — Propagate negotiated version at load time (https://github.com/10gen/mongo/pull/64623)
* [SERVER-137781|https://jira.mongodb.org/browse/SERVER-137781] — Make DB Integration & Observability own jstests/core/diagnostics (https://github.com/10gen/mongo/pull/64021)
Components
Diagnostics
Fixed Versions
9.1.0-rc0
SERVER-138130ClosedDone
Feature branch ticket for merge-main-staging-poc-2026-10-27
Fixed Versions
9.1.0-rc0
SERVER-73897ClosedFixed
Resharding coordinator returns generic abort error after recovery from stepdown
When resharding aborts, it stores the abort reason in the coordinator document. If it steps down and restarts again, it will [abort the cancel token|https://github.com/mongodb/mongo/blob/3d262046a212691cb18fd062a7f186bf81cf6b56/src/mongo/db/s/resharding/resharding_coordinator_service.cpp#L1846] when it sees that the state is aborting. This in turn will cause it to get callback cancelled error later (I suspect from [here|https://github.com/mongodb/mongo/blob/3d262046a212691cb18fd062a7f186bf81cf6b
Components
Sharding
Fixed Versions
8.1.0-rc08.0.0-rc8
SERVER-121172ClosedWon't Fix
Documentation Updates
This ticket is to update all types of documentation API Guide,
Programming Guide, and Architecture Guide related to the project.
SERVER-121170ClosedWon't Fix
Enable feature flag
Enable the feature flag for this project.
SERVER-121169ClosedWon't Fix
Create feature flag
Create the feature flag for this project.
SERVER-121171ClosedWon't Fix
Grammar fuzzer changes
Grammar fuzzer changes for this project.
SERVER-121173ClosedWon't Fix
Multiversion and Upgrade/Downgrade Testing
This ticket is to ensure there is adequate multiversion testing
coverage for this project.
1. Test that this feature works correctly on mixed binary version
clusters.
2. Test how the feature behaves when upgrading FCV turns the
feature on
3. Test that the correct behavior occurs when downgrading FCV
completely and then upgrading FCV completely
4. Test that the correct behavior occurs if the FCV upgrade fails.
5. Test that the correct feature behavior occurs if the FCV downgrade
fails after only
SERVER-137935ClosedFixed
Add rebase merge validation to match squash merge coverage
Anything in this description will be included in the commit message. Replace or delete this text before merging. Add links to testing in the comments of the PR.
h2. Description
*Problem*
Squash merge collapses a pull request into one commit, so the existing {{validate_commit_message}} task validates the squashed headline (title + description) and gets full coverage with a single check. If the repo moves to rebase-and-merge, each PR commit lands verbatim, which loses coverage:
* intermediate comm
Components
Build
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138191ClosedFixed
Run commit validation as GitHub Actions
h2. Description
{{buildscripts/validate_rebase_merge.py}} currently only runs inside Evergreen patch builds, which adds a task to every PR's patch build. This PR makes it an on-demand GitHub Action instead:
* New {{.github/workflows/validate-rebase-merge.yml}} (modeled on {{fast-forward-merge.yml}}): a PR comment of exactly {{/validate_rebase_merge}} runs the script, reacts 🙈→👍/👎 to the triggering comment, and posts the failure output on the PR. It runs on the codebuild runner and sends Honey
Components
Bazel
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137614ClosedFixed
Add `showEndOfTransaction` change stream option
This change adds an `showEndOfTransaction` option to change streams.
The option has values `off`, `whenAvailable` and `required`. Not setting the option is identical to `off`.
The option value is only serialized and affects the query shape hash if it is set to `whenAvailable` or `required`. This keeps compatibility with older versions.
The option can only be set if the feature flag `featureFlagChangeStreamEventOfTransactionEventSynthesis` is enabled, and if a v2 change stream reader can be us
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-130084ClosedFixed
Add support for "just log" semantics from message filter hooks
There is interest in adding support for message filter hooks that just log when a pattern is detected but otherwise do not interfere with the operation. Neither throwing or closing the connection. This is primarily for cases where a pattern is "suspicious" but not a clear exploit, and we want to know how common it is before we consider rejecting.
Proposal: Use negative values of hook returns to signify that the plugin deems some case worthy of logging but not rejecting. We already treat zero
Fixed Versions
8.0.297.0.409.0.0-rc18.3.8
SERVER-137244ClosedFixed
Clean up HistogramServerStatusMetric::pow
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137224ClosedFixed
Fix preproccessOplogEntry() perf regression
In BF-46813, we are seeing significant overhead from parsing oplog entries in {{{}preproccessOplogEntry(){}}}.
!Screenshot 2026-10-22 at 11.26.46 AM.png|width=542,height=429!
!Screenshot 2026-10-22 at 11.29.08 AM.png|width=542,height=429!
We need to avoid parsing every op in an applyOps entry if we have concluded it is not a checkpoint.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138220ClosedFixed
Fix POA backpressure log statement mixing size_t and uint64_t in std::min
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136844ClosedFixed
Avoid limit 1/coscan pattern in SBE
SBE still often uses the {{limit 1/coscan}} pattern to feed non-leaf stages data. This is often pretty expensive. We should replace uses of this pattern with either:
* A virtual scan (taking care to productionize the stage)
* A single coscan-n stage
A goal of this ticket is to remove the {{makeLimitOneCoscan()}} utility code.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-135599ClosedFixed
Invalidate plan cache when validator-inferred types change
Validator MatchExpression inference produces a SchemaTypeInfo containing inferred field types used by query planning optimizations. When the collection validator or validation level changes, these inferred types may become stale while existing cached plans continue to be reused.
Update plan-cache invalidation so that changes to validator-derived inferred types invalidate affected cached plans. Initially, use collection-wide invalidation by reusing the existing collection cache invalidation me
Fixed Versions
9.1.0-rc09.1.0-rc1025