Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138048ClosedDuplicate
test_change_stream_sharding_fsm_resume.js AND test_change_stream_sharding_fsm_continuous.js fail on a duplicate reshardCollection event when the resharding commit is retried
The change stream FSM verifier asserts that the stream delivers _exactly one_ {{reshardCollection}} event per resharding command. The server is allowed to emit more than one: the commit notification is sent at the start of {{{}ReshardingCoordinator::_commitAndFinishReshardOperation{}}}, which is retried as a unit on transient errors, and the code comment in {{src/mongo/db/s/resharding/resharding_coordinator.inl}} (introduced by SERVER-113247) says "multiple copies of this event notification are
CSHARP-6295Ready for Work
Publish the MongoDB provider for Microsoft.Extensions.VectorData as an official NuGet package
The MongoDB provider for Microsoft.Extensions.VectorData lives in mongodb/mongo-mevd-provider and isn't yet released. It needs to be published to NuGet as an officially supported MongoDB package, so .NET users can use MongoDB as a vector store through the VectorData abstractions.
SERVER-138049In Code Review
Allocate individual thread pools per resharding operation
Concurrent reshardings on distinct namespaces (see SERVER-136621) currently share a single PrimaryOnlyService thread pool per service. The coordinator admission cap {{max(1, (reshardingCoordinatorServiceMaxThreadCount - 1) / 3)}} exists only to keep concurrent operations from starving each other on that shared pool. Give each resharding operation its own thread pool, so concurrency scales until machine resources are the limit. the follow up work will remove the cap's dependency on MaxThreadCount
Fixed Versions
9.1.0-rc0
NODE-5085Backlog
Setup evergreen project trigger for any BSON changes in driver CI
h3. Use Case
As a node driver engineer
I want to know if BSON changes will impact the driver
So that we can be aware of issues before releasing BSON
h3. Dependencies
* It would be nice to add a BSON tgz upload task
** So the driver doesn't need to install bson's dev deps and run bundling
h3. Unknowns
* Can another EVG project easily pull in assets uploaded in another project's task?
h3. Acceptance Criteria
h3. Implementation Requirements
* Add trigger to driver CI that fires w
Components
CITesting
NODE-6601Backlog
Remove dependence on runtime specific APIs
{panel:bgColor=#fafbfc}
h3. *Summary*
Developer tools applications have had various needs for being able to customize the driver's I/O functionality, in particular around network connectivity/DNS resolutions. This project aims to provide an API for applications to provide their own implementations of these methods.
Primarily, this would be about methods currently imported from the {{{}net{}}}, {{tls}} and {{dns}} Node.js core packages. Additionally, it may be worth keeping in mind that th
Components
Connection Layer
NODE-7832Backlog
Missing required sub-document 'driver' in the client metadata document when using jest
h3. Expected Behavior
As a... Node Driver developer
I expect... driver to load correctly when `require` is available but dynamic-import callback is not
When... using driver 7.6 or higher
h3. Actual Behavior and Impact
* Current experience: `MongoServerError: Missing required sub-document 'driver' in the client metadata document`
* This is incorrect and a red herring, forcing a user on a useless investigation
* Workaround: setting `runtimeAdapters: \{ os: require('os') }` as a connect
Components
Connection Establishment
Affected Versions
7.6.0
NODE-7629Backlog
Add actionable hint to querySrv ECONNREFUSED errors for Windows-Node DNS known issue
{panel:title=Summary}
Add a hint to {{ECONNREFUSED}} errors when the runtime combination matches the known issue from [Node.js Windows DNS resolver|https://github.com/nodejs/node/pull/61453], so users and AI agents stop spending time troubleshooting (see sample Reddit [post|https://www.reddit.com/r/mongodb/comments/1u4b9z4/i_spent_4_days_debugging_mongodbs_econnrefused/]).
{panel}
h2. Background
Users connecting to MongoDB Atlas via {{mongodb+srv://}} on Windows frequently hit:
This has
Components
SRV Polling
NODE-7829Backlog
Pin exact drivers-github-tools versions ahead of v4
This ticket was split from {{DRIVERS-3633}}, please see that ticket for a detailed description.
Components
GitHub Tools
NODE-7592Backlog
npm 12 compatibility: migrate native addons off prebuild-install
h3. Use Case
As a... Node driver user and maintainer
I want... our packages to install and run correctly under npm 12
So that... users on the latest npm are not silently broken
npm 12 blocks dependency install scripts by default. Our native addons (zstd, kerberos, mongodb-client-encryption) fetch their binary via a prebuild-install install script, so under npm 12 the install "succeeds" but no binary is delivered and the module fails to load at runtime. They are optional peer deps of the
NODE-7779Backlog
Spike: Use typed accessors to handle response data
h3. Use Case
As a... Node Driver developer
I want... the Driver to use typed accessors to access parsed responses
So that... Node Driver doesn't have to deal with all possible representations of BSON data
h3. User Experience
* End-user sees the same behavior
* Node Driver developer is able to retrieve number responses without needing to care how the data is parsed, which changes depending on which BSON options the user passes along
h3. Dependencies
* None
h3. Risks/Unknowns
*
NODE-7929ClosedDuplicate
Clean up the connection in case of CSOT timeout
h3. Use Case
As a developer using timeoutMS,
I want a connection to be closed when an operation times out after its command was already written,
So that a later operation on that pooled connection never receives the earlier command's reply.
h3. User Experience
With timeoutMS set and a slow app-to-database link, a write that uses almost all of the time budget makes sendWire throw MongoOperationTimeoutError: Server roundtrip time is greater than the time remaining. The connection is not c
Components
CSOT
NODE-7958ClosedFixed
Make timeoutMS a no-op
h3. Use Case
As a... driver developer
I want... to make timeoutMS a no-op
So that... we are prepared to remove the feature entirely in a follow-up
h3. User Experience
Passing in timeoutMS does not set any mongoclient options and does not throw.
h3. Dependencies
* N/A
h3. Risks/Unknowns
* N/A
h3. Acceptance Criteria
h4. Implementation Requirements
* Make timeoutMS a no-op (ignore it when parsing the options, don't remove it entirely since we don't want it to throw)
* Mark
Fixed Versions
7.8.0
NODE-7966ClosedFixed
timeoutMS is deprecated backport in Node Driver to 6.22.0
h3. Use Case
As a driver maintainer
I want to backport timeoutMS deprecation into v6.22.0
So that the feature is consistently unsupported in v6 and v7
h3. User Experience
* timeoutMS is a deprecated no-op in v6
h3. Dependencies
* None
h3. Risks/Unknowns
* None
h3. Acceptance Criteria
h4. Implementation Requirements
* Backport NODE-7958 into 6.22.0
h4. Testing Requirements
* CI on backport branch needs to be green (tests should either be intentionally skipped as non
Components
node-driver
Fixed Versions
6.22.0
NODE-7863Backlog
Sustained heap and RSS growth while iterating large cursors with Node.js Driver v7
h3. Expected Behavior
As a... Node.js driver user iterating large result sets
I expect... memory used while iterating a cursor batch to stay bounded, regardless of how many documents the server returns per batch
When... consuming a {{find}}/{{aggregate}} cursor sequentially (async iteration or {{cursor.stream()}}) over many small documents without setting {{batchSize}}
h3. Actual Behavior and Impact
* {{OnDemandDocument}} caches every array element accessed by index ({{document.ts}}, num
Components
Cursors
Affected Versions
7.0.0
NODE-7698Backlog
Drop prefixPreview, suffixPreview, and substringPreview APIs
This ticket was split from {{DRIVERS-3548}}, please see that ticket for a detailed description.
*AC*
Update libmongocrypt to 1.21.1 because it's available (rather than 1.21.0)
NODE-7699Backlog
Support for Node.js 26
{panel:bgColor=#fafbfc}
h3. *Summary*
_What is the problem or use case, what are we trying to achieve?_
April-May 2026 Release, October LTS
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 t
NODE-7517Ready for Work
Adopt TypeScript 6.0
{panel:bgColor=#fafbfc}
h3. *Summary*
_Migrations to major versions of typescript become increasingly critical and more difficult the more major versions behind we are. As such, we should strive to stay at least one major version behind critical build tooling packages like typescript, as they directly affect maintainability of our product, and risk emergent problems when core features are sunsetted._
h3. *Motivation*
h4. Who is the affected end user?
_Driver engineers, driver users._
h
Components
TypeScript
SERVER-138502ClosedFixed
Wait for index build failpoint before renaming in rename_collection_with_in_progress_index_builds.js
The test rename_collection_with_in_progress_index_builds.js starts the rename too early. Its readiness check returns before the server has recorded the index, so the rename never fails fast as the test expects. The rename and the index build then wait for each other until Evergreen stops the task.
{{hangIndexBuildOnShard0()}} uses {{IndexBuildTest.waitForIndexBuildToStart()}} to decide the index build has started. That helper polls {{$currentOp}} for a {{createIndexes}} operation, which shard
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-6212Ready for Work
[Rust core] Define the scope of PyMongo with Rust Core and what ships alongside a Rust backend
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
SERVER-74031ClosedFixed
ReshardCollectionCoordinator should emit the op entry on its commit while still blocking user writes
Fixed Versions
7.1.0-rc0