Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138670ClosedFixed
Add a dead slot elimination rule for SBE blueprint projects
Add a blueprint rewrite rule that removes project entries whose slots nothing reads, and replaces a project left empty by its child. Some JOO queries spend about 10% of their time computing such slots.
* Give rewrite rules a shared slot summary ({{SbBlueprintSlotUsage}}) and a way to queue a node to be rewritten again
* Entries are removed even if evaluating them could raise an error
* Other node types are left for later
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136202ClosedFixed
Potential null pointer dereference in document_source_list_local_sessions.cpp
I found a potential null pointer dereference in {{{}src/mongo/db/pipeline/document_source_list_local_sessions.cpp{}}}.
[https://github.com/mongodb/mongo/blob/master/src/mongo/db/pipeline/document_source_list_local_sessions.cpp#L77-L102]
In the {{listSessionsRequiredPrivileges}} function, the return value of {{Client::getCurrent()->getOperationContext()}} is passed to {{getUserNameForLoggedInUser()}} without being checked for nullptr:
{{const auto& myName =
getUserNameForLoggedInUse
Affected Versions
8.0.9
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138667ClosedFixed
Harden resharding recipient step-up deadlock test to exclude idle clients
In the SERVER-127745 regression test, {{getReshardingRecipientServiceOps()}} uses {{$currentOp}} with {{idleConnections: true}} and filters only by client description. This can include idle recipient-service clients without an OperationContext or {{opid}}.
Those entries may satisfy the three-second stability check before the rebuilt recipient instance reaches the index-build wait. The second failover could consequently miss the intended regression scenario.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136222ClosedFixed
Introduce separate parameters for grid connection pools
SERVER-95057 made the grid connection pool use the MinPoolSize or MinPoolSizeForConfigServer parameters to address outage. However, this created a possibility of connection storms on the config nodes if the parameters are not correctly configured following an upgrade. We should introduce new parameters (default of 1 and 32767, same as the pool size parameters) specifically for this connection pool.
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
NODE-7932ClosedWon't Fix
Add serverSelector MongoClient option to target one replica set member or mongos
h3. Use Case
*As a* driver user
*I want* a {{serverSelector}} function option on {{MongoClient}} that narrows server selection to a specific member of a replica set or a specific mongos
*So that* I can target one member while the driver keeps discovering the rest of the deployment (unlike {{{}directConnection{}}}, which forces a Single topology and skips discovery). Matches PyMongo's {{{}server_selector{}}}.
h3. User Experience
Not a URI option, since the value is a function. Omitting t
SERVER-119744ClosedFixed
Unreplicated db.system.profiling may cause DatabaseDifferCase
Currently, the {{<db>.system.profiling}} collection is not replicated, which means it is possible to create an unreplicated database on a specific node in a replica set.
If the same database is later created on other nodes using different casing, that node will fail with a {{DatabaseDifferCase}} error, while the rest of the nodes in the replica set will succeed.
Fixed Versions
9.0.0-rc0
SERVER-121472ClosedFixed
The deterministic fuzzer jobs in evergreen use an old jstestfuzz git SHA
In order to ensure determinisim, in this commit:
deterministic fuzzer jobs were introduced that use a pinned version of the jstestfuzz repository (pinned to 8ddd8f12cab0).
Unfortunately that SHA is very old and {*}references python3.7, which is no longer available on the Windows evergreen runners{*}. A new jstestfuzz SHA needs to be used, some SHA that comes after this commit , which replaces the use of 3.7 with 3.10 in the jstestfuzz repository:
Components
Testing Infrastructure
Affected Versions
8.0.27
Fixed Versions
9.0.0-rc08.2.128.0.288.3.7
SERVER-132763ClosedFixed
Bump pinned jstestfuzz rev past package-lock artifactory fix
## Problem
All `*_fuzzer_deterministic` tasks are failing across master and every staging branch (BF-45305, ~580 failures since 2026-07-31) with:
```
npm ERR! 503 Service Temporarily Unavailable - GET https://artifactory.corp.mongodb.com/artifactory/api/npm/npm/y18n/-/y18n-4.0.3.tgz
subprocess.CalledProcessError: Command 'npm install' returned non-zero exit status 1
```
## Root cause
The fuzzer tasks clone `10gen/jstestfuzz` and then `git reset --hard` to the rev pinned by `--jstestfuzzGitRe
Components
evergreen.yml
Fixed Versions
8.2.139.1.0-rc08.0.309.0.0-rc2
GODRIVER-4244ClosedDone
Azure and GCP KMS tasks fail with "libssl.so.1.1: cannot open shared object file"
h3. *Name of Failure:*
libssl.so.1.1: cannot open shared object file
h3. *Link to task:*
https://spruce.corp.mongodb.com/task/mongo_go_driver_testazurekms_variant_testazurekms_task_3c254894621703106972d659cfeea33e9e55c103_26_11_05_16_26_25/logs?execution=1
h3. *Context of when and why the failure occurred:*
Seems to have started failing Sept 3 in [this build|https://spruce.corp.mongodb.com/task/mongo_go_driver_testazurekms_variant_testazurekms_task_3c87f2112f3fbd57f5f636c5c8f444e374f248
PYTHON-6088ClosedDone
Document changelog style guide
h3. *Context*
Our changelog entries don't follow a documented style. Contributors currently guess at tense, wording, and formatting, which leads to inconsistent entries across drivers and over time.
h3. *Definition of done*
A written style guide based on "Keep a Changelog" ([https://keepachangelog.com|https://keepachangelog.com/]) exists for changelog entries that defines tense, voice, level of detail, how to reference tickets/PRs, date format, ordering, etc.
This style guide should be
Components
Infrastructure
GODRIVER-4232ClosedDone
Run the OCSP responder setup in the foreground
h3. *Name of Failure:*
OSCP variants
h3. *Link to task:*
E.g. https://spruce.corp.mongodb.com/version/mongo_go_driver_release_46ea770625ac2d828f9c6d7a3dcaadb6de360e3c/tasks?page=0&sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC&variant=%5Eocsp-test__version~9.0_ocsp-rhel-87~rhel87%24
h3. *Context of when and why the failure occurred:*
Our CI starts ocsp/setup.sh in the background, so EG moves on to the orchestration and runs run-ocsp-test without waiting for the mock responder. The driver wil
Components
Evergreen
SERVER-134962ClosedFixed
Port advanceCheckpoint() tests to flusher test file
replicated_fast_count_advance_checkpoint_test.cpp contains exhaustive unit tests for advanceCheckpoint(), but this function is no longer used. Port these unit tests to the flusher test file to gain test coverage of the function we use to flush in steady state, flush().
Fixed Versions
9.1.0-rc09.1.0-rc1025
NODE-7945ClosedDone
kerberos - PR #373: chore(deps-dev): bump fast-uri from 3.1.5 to 3.1.9 in /test/bundling/webpack
[dependabot[bot]|https://github.com/apps/dependabot] has created [PR #373: chore(deps-dev): bump fast-uri from 3.1.5 to 3.1.9 in /test/bundling/webpack|https://github.com/mongodb-js/kerberos/pull/373] in [kerberos|https://github.com/mongodb-js/kerberos]
Fixed Versions
kerberos-7.1.0
NODE-7946ClosedDone
js-bson - PR #957: chore(deps): bump fast-uri from 3.1.8 to 3.1.9
[dependabot[bot]|https://github.com/apps/dependabot] has created [PR #957: chore(deps): bump fast-uri from 3.1.8 to 3.1.9|https://github.com/mongodb/js-bson/pull/957] in [js-bson|https://github.com/mongodb/js-bson]
Fixed Versions
bson-7.3.4
GODRIVER-4231Needs Triage
Unskip bulkWrite collectionUUID subtest when server bug is fixed
h3. *Context*
All subtests in the new test {{TestClient_BulkWrite_CollectionUUIDs}} added with GODRIVER-3699 are skipped on MongoDB 9.0+ sharded clusters because of an apparent bug in mongos that incorrectly deduplicates {{nsInfo}} documents in {{bulkWrite}} commands (see SERVER-138544). We should skip those
h3. *Definition of done*
* Once SERVER-138544 is resolved and released, update {{TestClient_BulkWrite_CollectionUUIDs}} to run on all MongoDB 8.0+ servers, all topologies.
h3. *Pitfa
GODRIVER-3699ClosedFixed
Allow collection UUIDs in Client.BulkWrite requests
GODRIVER-3582's original purpose was to allow internal users like C2C to pass arbitrary arguments to `bulkWrite` commands. That ticket's scope was later reduced to implementing a custom bypassEmptyTsReplacement parameter.
That doesn't solve our problem, however. We need to be able to pass arbitrary parameters in `bulkWrite` requests. (Or, as 3582 first requested, we need to be able to reuse the driver's parsing of `bulkWrite` cursor responses.) This will let us use undocumented (but mission-c
Components
Bulk APICRUD
Fixed Versions
2.10.0
SERVER-137516ClosedFixed
Disregard Temporary Collections in Manifest Validation for format testing (Complete TODO listed in SERVER-136251)
We had disabled a test for format testing because there were temporary collections being recorded in the manifests for each snapshot, and depending on when they were dropped, the manifests could show inconsistencies. Since these collections are temporary, they are not true indicators of successful snapshot restore, and can be ignored during manifest validation.
We could remove them from manifest collection, but we don't want to bump the version number and lose older snapshot manifests, so ins
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138255ClosedFixed
Extend timeout in ocsp_basic_ca_responder.js
[BF-47001|https://jira.mongodb.org/browse/BF-47001]: {{ocsp_basic_ca_responder.js}} failed on enterprise-windows (v8.3-staging @ 5d60fa4c) with {{did not throw exception}} at line 52, during the second {{test()}} call (intermediate-CA chain). The shell connected to mongod even though the mock OCSP responder was set to report the server cert as revoked.
h3. Likely cause
The shell's revocation check seems to have hit the 4s default {{tlsOCSPVerifyTimeoutSecs}} (passed to Windows as {{{}dwUrlRe
Fixed Versions
9.1.0-rc09.1.0-rc1025
NODE-7975ClosedDone
node-mongodb-native - PR #5096: chore(v6.x): release 6.22.0
[github-actions[bot]|https://github.com/apps/github-actions] has created [PR #5096: chore(v6.x): release 6.22.0|https://github.com/mongodb/node-mongodb-native/pull/5096] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
Fixed Versions
6.22.0
NODE-7976ClosedFixed
kerberos - PR #378: chore(deps-dev): bump follow-redirects from 1.16.1 to 1.16.2
[dependabot[bot]|https://github.com/apps/dependabot] has created [PR #378: chore(deps-dev): bump follow-redirects from 1.16.1 to 1.16.2|https://github.com/mongodb-js/kerberos/pull/378] in [kerberos|https://github.com/mongodb-js/kerberos]
Fixed Versions
kerberos-7.1.0