Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-136703ClosedFixed
Implement stand-alone MCV
Maintain a fixed-size heavy hitter (Top-K) key map for the heavy head skewed data during the statistics scan/sample. We will need to use streaming techniques like the Space-Saving algorithm to compute the top-K MCVs within an O(K) space bound, regardless of how large the NDV count of the column is.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137769ClosedDone
Compare MCV implementations
Compare the implementations of the Most common values statistics collection using BSONObj and SBEValues.
SERVER-138388ClosedFixed
Add test covering change stream updateLookup fullDocument for shard-key-changing updates (legacy vs optimized)
h2. Overview
Add a regression test pinning the update event's {{fullDocument}} for updates that change the shard key, with {{fullDocument: "updateLookup"}}, comparing the optimized updateLookup flag on and off.
h2. Background
[REP-8114|https://jira.mongodb.org/browse/REP-8114] (mongosync server-side hashing) found update events whose shard key value changed arriving without a {{fullDocument}} on released 9.0.x. That is the legacy lookup's design: it matches on the event's {{documentKey}}, which
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136906ClosedFixed
Memory Tracker API
Query memory tracking charges each byte at a checkpoint. We plan to charge some data types at allocation instead, and each byte must then count once toward the per-operation limit. To do that, a tracker needs two figures for the bytes it holds:
* full: everything the stage holds. Spilling decisions and a stage's own limit use this.
* unique: the part not already charged to the operation tracker at its allocation. The operation tracker's total and per-operation limit use this, so a byte charg
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-122127ClosedFixed
Allow killop to accept an array of opIds
Currently, the killop command only accepts a single opId. As a result, when Query Sentinel tries to kill a batch of queries, it has to issue a killop for each query, which slows down QS. Instead, we will allow the killop command to accept a batch of opIds to kill.
Fixed Versions
9.0.0-rc0
SERVER-138362ClosedFixed
Remove remaining invariant calls in change streams pre-image code
Remove all remaining {{invariant()}} calls in change stream pre-images code, outside of tests and benchmarks.
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138136ClosedDuplicate
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
SERVER-137781ClosedFixed
Make DB Integration & Observability own jstests/core/diagnostics
h2. Overview
Give the DB Integration & Observability \(DINO\) team ownership of the {{jstests/core/diagnostics}} test directory, replacing the previous mixed/unowned state.
h2. Background
Tests under {{jstests/core/diagnostics}} cover diagnostics and observability functionality owned by DINO, but the directory was not assigned to the team in CODEOWNERS, so changes there did not reliably route to the owning team for review.
h2. Scope of Work
\* Add an {{OWNERS.yml}} for {{jstests/core/diagnosti
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138286ClosedDuplicate
CheckMetadataConsistency on secondaries: release CSR when checking the shard catalog
Secondaries don't rely on the CSR to keep the catalog stable, and since they read with snapshot read concern, holding the CSR can lead to deadlocks.
SERVER-129618ClosedFixed
Disallow user-provided $vectorSearch args from overriding internally generated options
An option like 'viewName' or 'collectionUUID' is only intended for the server to use/generate. We need to better enforce that a user cannot manipulate these values.
Fixed Versions
8.2.138.0.297.0.409.1.0-rc08.3.89.0.0-rc2
SERVER-135099ClosedFixed
Disable IFR flag featureFlagChangeStreamReaderV2
Temporarily disable the IFR flag {{featureFlagChangeStreamReaderV2}} to avoid a potential post-batch resume token regression issue in sharded cluster change streams.
When resuming a change stream in a sharded cluster on mongos using a change event resume token (via {{resumeAfter}} / {{startAfter}}), the change stream was internally resumed with a high watermark (HWM) token instead of the actual event token. The HWM token has the same cluster time value as the original event resume token, but s
Components
Change streams
Fixed Versions
9.0.2
SERVER-127946ClosedFixed
Renew all test certs for 7.x, 8.x, 9.x
The x509_expiring task is failing in recent patches:
* [https://spruce.corp.mongodb.com/version/6a1c42e7b5175000070d5133]
* [https://spruce.corp.mongodb.com/version/6a1c443ffe2147000701fd2b]
I see SPM-3882 is in progress, but until that's done it looks like the renewals still have to be done manually.
Fixed Versions
8.2.137.0.418.0.308.3.139.0.4
SERVER-120651ClosedWon't Do
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-120650ClosedWon't Do
Documentation Updates
This ticket is to update all types of documentation API Guide,
Programming Guide, and Architecture Guide related to the project.
SERVER-138458ClosedFixed
Make jsobjtests write corrupt BSON consistently across platforms
This dbtest uses a BSONObj with a corrupt size. On little endian systems, the corruption is in the form of it over-reporting its size, so the same message is still thrown. On big endian systems, the corruption is in the form of it reporting a negative size, so that message isn't thrown (a different one appropriate to the situation is though, so no bug).
This change fixes the test so it works consistently no matter the endianness of the host system.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136771ClosedDone
Complete TODO listed in SERVER-130286
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/modules/atlas/src/disagg_storage/pali/log_server_connection.cpp:266
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-130286&type=Code
The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of th
SERVER-138380ClosedFixed
Add default PATH for podman client in Linux container action wrapper
{{bazel build install-devcore}} fails with rootless podman 3.4.4 (Ubuntu 22.04):
{{nsenter}} is installed. The {{MongoInstallRule}} action runs under {{exec env -}}, so it has an empty environment and no {{PATH}}. {{_container_runtime_env}} in {{linux_container_action_wrapper.py}} copies {{os.environ}} into the environment of its {{podman}} calls. Podman 3.4.4 looks up {{nsenter}} through {{PATH}} when setting up CNI networking, so the call exits with 125.
{{_container_runtime_env}} now applie
Components
Bazel
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138244ClosedFixed
Add new IDL type carrying resharding server parameters
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137376ClosedFixed
Refactor ReadyRangeDeletionsProcessor to use a dispatcher and single-worker thread pool
Refactor the ReadyRangeDeletionsProcessor to use its existing thread as the dispatcher and process ready tasks through a single-worker pool, preserving existing behavior.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138381ClosedFixed
Synthesize endOfTransaction marker from applyOps
For replica set and single shard transactions, gate the synthesis of the {{endOfTransaction}} change events on the {{allowEndOfTransaction}} flag in the final applyOps oplog entry if the change stream is opened with the {{showEndOfTransaction}} option set to {{whenAvailable}} or {{required}} and both the server parameter {{allowEndOfTransaction}} and the feature flag {{featureFlagEndOfTransactionEventSynthesis}} are enabled.
The legacy path for emitting {{endOfTransaction}} events from the fina
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025