Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138407ClosedFixed
Re-exclude findAndModify_update_grow.js from disagg_concurrency_simultaneous until BF-45295 is fixed
h2. Overview
Temporarily re-exclude [findAndModify_update_grow.js|https://github.com/10gen/mongo/blob/9d5269427e60f18b9468a3da1abbc65d0f892fdd/jstests/concurrency/fsm_workloads/query/findAndModify/findAndModify_update_grow.js] from the {{disagg_concurrency_simultaneous}} suite as a mitigation for the hot build failure BF-45295, until the underlying fix lands.
h2. Background
BF-45295: {{disagg_concurrency_simultaneous}} on {{enterprise-amazon-linux2023-arm64-disagg-no-feature-flags-extra-system-
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-134609ClosedFixed
Complete TODO listed in SERVER-132391
There is a TODO in the codebase referencing a resolved ticket which is assigned to you.
Please follow this link to see the lines of code referencing this resolved ticket:
https://github.com/10gen/mongo/search?q=SERVER-132391&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 this ticket to represent the work you're actually doing.
Fixed Versions
9.1.0-rc0
PYTHON-6220Blocked
Bundle libmongocrypt 1.22.0
Update [pymongocrypt|https://pypi.org/project/pymongocrypt/] to bundle libmongocrypt 1.22.0.
Components
pymongocrypt
NODE-7971Blocked
Update libmongocrypt to 1.22.0
Update [mongodb-client-encryption|https://www.npmjs.com/package/mongodb-client-encryption] to bundle libmongocrypt 1.22.0
JAVA-6359Blocked
Update libmongocrypt to 1.22.0
Update [mongodb-crypt|https://mvnrepository.com/artifact/org.mongodb/mongodb-crypt] to bundle libmongocrypt 1.22.0.
CSHARP-6290Blocked
Update libmongocrypt to 1.22.0
Update [MongoDB.Driver.Encryption|https://www.nuget.org/packages/MongoDB.Driver.Encryption/] to bundle libmongocrypt 1.22.0.
SERVER-134042ClosedFixed
Write collection metadata watermark entry on checkpoint
Introduce a no-op watermark that marks the cutoff point for an upcoming replicated size and count checkpoint. This work includes persisting the watermark prior to the size and count checkpoint flushed at a regular cadence.
This establishes a concrete marker for associating each checkpoint with a corresponding sequence of replicated operations. The marker will support future continuous validation of collection hashes and cumulative size and count across nodes.
Fixed Versions
9.1.0-rc09.1.0-rc1024
SERVER-138387ClosedFixed
Fix MatchExpression ownership in matcher_typing_test.cpp
This is a test-only issue.
MatchExpression doesn't hold ownership of the BSONObj.
The test parses the MatchExpression with a temporary BSONObj which broke ASAN in SERVER-134938 when a MatchExpression with an unowned view into the BSON was added. This caused the auto-revert.
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-4877Ready for Work
python3 process shutdown is unreasonably slow after MongoClient (500ms)
h3. Detailed steps to reproduce the problem?
Prior to creating a MongoClient object, exiting the python3 process is reasonably fast at ~75ms (about ~60ms of which can be attributed to pymongo):
However, once a MongoClient object has been created, the time increases significantly by ~500ms:
I can see from the mongod logs that a connection is opened and closed 1-2ms later. But the problem occurs strictly during the python3 process shutdown (ie. calling {{.close()}} on the Mongo
SERVER-85637ClosedFixed
Remove Feature Flag for PM-3296
Feature flags should be proactively removed to address technical debt.
See the [Feature Flag Github page|https://github.com/mongodb/mongo/blob/master/src/mongo/db/repl/FCV_AND_FEATURE_FLAG_README.md#feature-flags] for additional guidance.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-135619ClosedFixed
Bump mongot-extension version to v2.0.7
Bump mongot-extension version to v2.0.7 to pick up byte caps on $rerank stage from CLOUDP-445731.
*Why*
The byte cap is to address unbounded memory risk for $rerank. More details can be found in this [doc](https://docs.google.com/document/d/1OEWnBb4euGz8unY5-MDFDVKaL7d53tkhqBI9-ha128A/edit?tab=t.0#heading=h.s8nex0ct7vpx)
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.7
SERVER-136032ClosedFixed
Bump mongot-extension version to v2.0.8
Bump mongot-extension version to v2.0.7 to pick up additional metric change for $rerank MTM OOM alerting from CLOUDP-452181
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.7
SERVER-137889ClosedFixed
Bump mongo-task-generator to v3.10.0
Bumps {{setup_mongo_task_generator}} in {{evergreen/prelude_mongo_task_generator.sh}} from v3.9.0 to [v3.10.0|https://github.com/mongodb/mongo-task-generator/releases/tag/v3.10.0], used by {{evergreen/generate_version.sh}} and {{evergreen/generate_version_burn_in.sh}}.
Picks up https://github.com/mongodb/mongo-task-generator/pull/123: generated tasks tagged {{requires_large_host}} are now routed to their build variant's large distro, matching the routing the variant's task selectors give static
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-122009ClosedWon't Fix
Mixed-version upgrade test for extension optimizations with feature flag
This is a placeholder ticket. The work for mixed version cluster scenario testing as it relates to extensions optimizations should be done by the extensions search team on Atlas. As per the design:
The most interesting case to test will be a mixed version cluster scenario. Specifically, we will have the case where the router/mongos is going to be doing one pass of optimizations on the old extension, and then they will serialize themselves on that older version, and have the shards digest that
SERVER-133023ClosedFixed
Background tasks may not be properly exempted from load shedding
Claude says:
There is an asymmetry in load shedding exemption logic:
- ordered_ticket_semaphore.cpp:26-33 sheds only if getLowAdmissions() == 0 && queue >= maxWaiters && !admCtx->isLoadShedExempt().
- unordered_ticket_semaphore.cpp:58-67 sheds on previousWaiters >= _maxWaiters alone — no isLoadShedExempt() check, and also no getLowAdmissions() == 0 check.
Git archaeology — it is an oversight, not a design choice
- UnorderedTicketSemaphore (with its overflow shed) landed 2026-03-02 in
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-115424ClosedWon't Fix
Investigate $limit vs $extensionLimit correctness in sharded collections
Both stages follow different execution paths and can return different results non-deterministically in a sharded collections topology. Investigate whether this discrepancy in results can be fixed on the extensions side (or if minimal server changes can be made that are specific to the extensionLimit stage).
If so, update the MatchTopN extension to use $extensionLimit (and its relevant tests) and the extension_limit.js test to assert on the results instead of just the result set lengths for sh
SERVER-137791ClosedFixed
Prevent deletes from being split from applyOps in version_context_oplog_entries.js
Deletes that should appear in a single {{applyOps}} can fall in different batches as separate oplog entries on slow machines in this test. Adjust the timing to prevent this.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-121825ClosedFixed
Make background operations bypass max queue length check
Currently we only allow bypassing the queue lenght operations that have been already admitted, however, background operations are server side maintenance tasks that should ensure some level of work over time, so, the purpose of this ticket is to allow background operations bypass that check, so they can be added to the queue and wait for tickets.
Fixed Versions
9.0.0-rc08.3.3
SERVER-109773ClosedFixed
Investigate possible memory leak when loading extensions
See SERVER-109351 for more context. This ticket tracks further investigating the original issue to verify the source of the leak (see comments for investigation next steps).
Fixed Versions
8.3.0
SERVER-135354ClosedFixed
Add a histogram which reports the number of operations run per connection
To get a better idea of how much we reuse connections, we should create a histogram for the number of operations run per connection. We could accomplish this by adding an OTel histogram to the ConnectionPool class.
Fixed Versions
9.1.0-rc09.1.0-rc1025