Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-120232ClosedFixed
Document why defaultStartupFCV is runtime settable
As part of https://jira.mongodb.org/browse/SERVER-110750 we changed defaultStartupFCV to make it run-time settable. The reason for this is a very specific request from the Atlas team. This should be documented in the parameter so that we keep the context of this decision.
Fixed Versions
9.1.0-rc09.1.0-rc1024
SERVER-127889ClosedFixed
Broken "feature compatibility" link in error message
I got this error in MongoDB 8.3.2:
but there is no "#feature-compatibility" on that page.
And MongoDB 8.0 gives this error:
Once again, the#feature-compatibility section seems missing from the linked page.
From a server documentation writer:
{quote}Well I _think_ there could be a few things going on here after poking around a bit: * I'm not too familiar with the upgrade procedure enhancements at a granular level, but I'm thinking that maybe the target anchor was removed for more
Affected Versions
8.3.28.0.23
Fixed Versions
9.1.0-rc09.1.0-rc1024
SERVER-138607ClosedFixed
Ensure FSM tests using renameCollection handle non-idempotency after failover
*Issue*
renameCollection is not idempotent, so if it is retried after a failover (stepdown/kill/retry), the retry can fail with a NamespaceNotFound error. So rename tests must either:
* Be excluded from stepdown suites, or
* Gracefully accept the NamespaceNotFound.
Some of our tests in jstests/concurrency do not follow this pattern (rather are only incidentally excluded for other reasons), so when new suites are added they start failing.
Some failures have been recently uncover
Components
Concurrency
Affected Versions
9.1.0-rc0
Fixed Versions
9.1.0-rc09.1.0-rc1025
GODRIVER-4241ClosedDone
Update github.com/xdg-go/scram to remove the github.com/xdg-go/pbkdf2 dependency
The latest version of the github.com/xdg-go/scram module (v1.4.0) exclusively uses the FIPS 140-3 certified stdlib "crypto/pbkdf2" implementation of the PBKDF2 key derivation algorithm, removing a dependency on the github.com/xdg-go/pbkdf2 implementation. Update to v1.4.0 and make sure it removes the github.com/xdg-go/pbkdf2 dependency.
h2. Definition of done
* Update the github.com/xdg-go/scram module to v1.4.0 or newer.
* Confirm that no Go Driver modules depend on github.com/xdg-go/pbkdf
Fixed Versions
2.10.0
NODE-7717Backlog
Release V8
h3. Use Case
Cut the V8 major of the driver and all supporting packages, keeping major versions aligned across the set.
h3. Acceptance Criteria
h4. Implementation Requirements
* Release alpha versions of the following:
* mongodb-client-encryption (8.0.0-alpha)
* kerberos (8.0.0-alpha)
* mongodb-connection-string-url (8.0.0-alpha)
* bson (8.0.0-alpha)
* zstd (8.0.0-alpha)
* Update driver main to use the above alphas
* Let shell and mongoose know which nightly build contains t
SERVER-138510ClosedFixed
primary_driven.js resume metric reader double-counts after OTel metrics file rotation
{{PrimaryDrivenResumableIndexBuildTest._readResumeMetrics()}} in {{jstests/noPassthrough/libs/index_builds/primary_driven.js}} assumes one OTel metrics file per node and sums the last cumulative snapshot of every file in the metrics directory. However, the OTel file exporter rotates files for a single node:
* at midnight UTC, because the file name embeds the date
({{mongodb-<pid>-%Y%m%d-%N-metrics.jsonl}}, see
{{src/mongo/otel/metrics/metrics_initialization.cpp}})
* when a file
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137979ClosedFixed
Join optimization propagates strict $expr semantics across localField/foreignField edge
{$expr: \{$eq: ["$x", null]}} on one side of a loose (null == missing) join is inferred onto the other node as \{$expr: {$eq: ["$y", null]}} by predicate_inferer.cpp. The inferred predicate rejects documents with a missing field that the loose join would have matched.
Fixed Versions
9.1.0-rc09.1.0-rc1025
NODE-7757ClosedWon't Do
Mark `authdb` and `dbName from CommandOperation for deprecation
h3. Use Case
As a... driver developer
I want... _to remove unused code paths_
So that... _I can reduce the complexity of the API surface we support_
h3. User Experience
* _`dbName` and `authdb`, two parameters in the public CommandOperation API but meant only for internal use, are marked as deprecated_
h3. Dependencies
* _authdb and dbName are used by removeUser, which should be marked for deprecation before this work_
h3. Risks/Unknowns
* _Confirm the non-use of authdb and dbN
NODE-6999Defining
Node V8
{panel:bgColor=#fafbfc}
h3. *Summary*
Release v8 of the MongoDB Node.js driver and supporting libraries.
h3. *Motivation*
h4. Who is the affected end user?
_Who are the stakeholders?_
h4. How does this affect the end user?
_Are they blocked? Are they annoyed? Are they confused?_
h4. How likely is it that this problem or use case will occur?
_Main path? Edge case?_
h4. If the problem does occur, what are the consequences and how severe are they?
_Minor annoyance at a log me
NODE-7756ClosedWon't Do
Remove `removeUser`
h3. Use Case
As a... driver developer
I want... _to remove unused code paths from the driver_
So that... _to reduce the complexity of the API surface we support_
h3. User Experience
*
h3. Dependencies
* _removeUser should have been marked for deprecation. Now, remove it._
h3. Risks/Unknowns
* _none_
h3. Acceptance Criteria
h4. Implementation Requirements
* _functional reqs, potential snafus to avoid, performance targets, etc_
h4. Testing Requirements
* remove tests
NODE-7755ClosedWon't Do
Mark `removeUser` for deprecation
h3. Use Case
As a... driver developer
I want... _to remove unused code paths_
So that... _I can reduce the complexity of the API surface we support_
h3. User Experience
* the *removeUser* function, its corresponding options and tests, are deprecated and ready for removal at the next major version.
h3. Dependencies
* _none_
h3. Risks/Unknowns
* _confirm the non-use of removeUser internally_
h3. Acceptance Criteria
h4. Implementation Requirements
* _none_
h4. Testing Req
NODE-5886Backlog
Consolidate URI and Client Options
h3. Use Case
As a Node.js deveoper
I want proper URI and MongoClient options
So that I can leverage different driver and Node native options.
h3. User Impact
* Customers passing Node native TLS options in the URI via mongosh
* A misplaced option throws, consistent with the existing hardcoded cases in connection_string.ts (serverApi in the URI, loadBalanced in the constructor)
h3. Dependencies
* _None_
h3. Unknowns
* _None_
h3. Acceptance Criteria
h4. Implementation Requir
Components
Connection String
NODE-7719Backlog
[Mastra] Update mongo's tests to support arbitrary (hence remote) URI
h2. Context
The existing structure of our vector tests in mastra hardcode the uri to mongodb://localhost:27017 / :27018.
h2. Definition of Done
# Confirm whether this hardcode exists only in the tests. If not, refactor the store's api.
# Refactor tests.
# Add test-mastra-js-remote to ai-ml-pipeline-testing.
Components
ABX
NODE-5689ClosedWon't Do
Remove deprecated timeout options and legacy timeout handling code
h3. Use Case
As a... _(who is this for)_
I want... _(what is the desired change)_
So that... _(why is the change desired)_
h3. User Impact
* _What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?_
h3. Dependencies
* _upstream and/or downstream requirements and timelines to bear in mind_
h3. Unknowns
* _questions that need to be answered to determine implementation_
h3. Acceptance Criteria
h4. Implementation Requirements
* _functi
NODE-7714Backlog
Update peer dependency versions for driver V8
h3. Use Case
As a driver engineer and user of the driver,
I want to have an up-to-date version support specification,
So that I stay ahead of any deprecations and can make use of improvements
h3. User Experience
* n/a
h3. Dependencies
* n/a
h3. Risks/Unknowns
* @aws-sdk/credential-providers is constrained by the SDK version bundled in the AWS Lambda Node runtimes. AWS no longer publishes this value; it varies by runtime version and Region and [has to be probed|https://docs.aws.
SERVER-138541ClosedFixed
Exclude system.resharding. from collection enumeration in test tooling
system.resharding.* collections were not excluded from enumeration in test tooling, leading to failures of some tests.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-112325ClosedFixed
Remove remainders of DocumentSourceChangeStreamCheckTopologyChange
[SERVER-111727|https://jira.mongodb.org/browse/SERVER-111727] changes the change stream pipeline building code for sharded clusters to that the {{DocumentSourceChangeStreamCheckTopologyChange}} stage is not included anymore in sharded cluster change streams, and turns that stage into a no-op stage.
SERVER-111727 cannot remove the stage entirely because older versions of mongos may still build change stream pipelines including that stage.
An old version of mongos can include the stage in the
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025