Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
NODE-7983ClosedDuplicate
node-mongodb-native - PR #5105: fix: do not check out a connection from a retired pool generation
[tap1r|https://github.com/tap1r] has created [PR #5105: fix: do not check out a connection from a retired pool generation|https://github.com/mongodb/node-mongodb-native/pull/5105] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
NODE-7982ClosedDuplicate
node-mongodb-native - PR #5104: fix: remove auto-encryption listeners when the user client removes them
[tap1r|https://github.com/tap1r] has created [PR #5104: fix: remove auto-encryption listeners when the user client removes them|https://github.com/mongodb/node-mongodb-native/pull/5104] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
NODE-7981ClosedDuplicate
node-mongodb-native - PR #5103: fix: keep sampling round-trip time after a failed measurement
[tap1r|https://github.com/tap1r] has created [PR #5103: fix: keep sampling round-trip time after a failed measurement|https://github.com/mongodb/node-mongodb-native/pull/5103] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
NODE-7980ClosedDuplicate
node-mongodb-native - PR #5102: fix: compare session idle time without folding it modulo one hour
[tap1r|https://github.com/tap1r] has created [PR #5102: fix: compare session idle time without folding it modulo one hour|https://github.com/mongodb/node-mongodb-native/pull/5102] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
SERVER-136206ClosedWorks as Designed
Updates return KeyExists (484) to the client when an index insert hits an existing key+RecordId — doUpdate lacks the tolerance added in SERVER-128827
h2. Summary
Updates can fail with {{\{code: 484, codeName: "KeyExists"\}}} on a 9.0 node when an index insert encounters an existing entry with the exact same key and RecordId. Prior to 9.0 this condition was a silent no-op and the update succeeded.
*This blocks mongosync’s 9.0 support* because it seems this will cause mongosync to fail unpredictably.
h2. Observed failure
Seen in the mongosync patch build for [mongosync PR #6039|https://github.com/10gen/mongosync/pull/6039] ([REP-7832|ht
SERVER-138129ClosedFixed
mongo-task-generator generated tasks should have a Jira assignment tag
Components
Testing Infrastructure
Fixed Versions
9.1.0-rc0
PYTHON-6127Defining
Use Proper English Grammar in Comments and Docstrings
{panel:bgColor=#fafbfc}
h3. *Summary*
_What is the problem or use case, what are we trying to achieve?_
{color:#172b4d}_go through the repositories and ensure that comments and docstrings adhere to proper english grammar as set out in the[ python coding principles doc|https://docs.google.com/document/d/1cj7qoD6uEE7A1FAuQm9plOwPBjgm-06vUs5VzgDDp3o/edit?tab=t.0]._{color}
h3. *Motivation*
h4. Who is the affected end user?
_Who are the stakeholders?_
h4. How does this affect the end use
Components
Infrastructure
SERVER-137323ClosedFixed
Record event identity and signal failures at the writing points
h2. Deliverable
Record the in-flight event identity and signal failures without building an event.
* *Transform stage:* Record each event’s identity as it is built, and clear the identity slot before pulling the next entry.
* *Pre-image, post-image, and updateLookup stages:* On a convertible lookup failure, set {{activeChangeStreamErrorSource = internal-pipeline}} and rethrow. Do not build the event.
* *BatchedEnrichmentStage (batched updateLookup):* Record each event’s identity bef
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136635ClosedFixed
Isolate GCP OIDC helper dependencies from the resmoke environment
h2. Problem
The {{external_auth_oidc_gcp}} task on v8.3-staging and v9.0-staging fails before any tests run because GCP setup installs unpinned dependencies into the shared resmoke virtual environment.
{{evergreen/external_auth_gcp_setup.sh}} runs {{python -m pip install google-cloud-compute}}. Its transitive {{google-api-core}} dependency upgrades {{opentelemetry-api}} while the locked {{opentelemetry-sdk}} and exporter remain at 1.35.0. The timeout helper imports resmoke's FileSpanExporter an
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.98.3.18
SERVER-137373ClosedFixed
Use the collection schema inferred type in the dependency graph
The DependencyGraph should have access to the inferred Type instance.
This ticket involves updating the DependencyGraph constructors to accept a callback which can lazily request the Type.
When the schema type is accessed, the ExpCtx marks it as used. A callback allows us to write the graph code such that we only access the schema type when we need it's type information.
Fixed Versions
9.1.0-rc09.1.0-rc1025
CSHARP-6240ClosedDone
Address flakiness in command logging, retryable reads, and retryable writes unified tests for retryable handshake errors
This ticket was split from {{DRIVERS-3206}}, please see that ticket for a detailed description.
Components
Retryable Reads & Writes
NODE-7781ClosedDone
[Mastra] Auto Embeddings for Semantic Recall
h2. TL;DR
When a Mastra {{Memory}} uses {{MongoDBVector}} with Automated Embedding, semantic recall should let MongoDB embed messages and queries *server-side* instead of requiring a client-side {{{}embedder{}}}. Today the docs and code both require an {{{}embedder{}}}, and the {{SemanticRecall}} processor always embeds client-side and passes a numeric {{{}queryVector{}}}, so it can't benefit from server-side embedding. Depends on NODE-7734.
h2. Context
*What semantic recall is.* Mastra's
Components
ABX
SERVER-138773ClosedFixed
Add ChangeStreamEndOfTransactionBackfillRequired error type
Add a new {{ChangeStreamEndOfTransactionBackfillRequired}} error type with additional payload that change streams can use to signal that they need to re-read previous parts of the oplog.
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136197ClosedDone
PoC for ChangeStream don't fail
Tracks the work needed to finalize the design via a PoC. Which will lead to project delivery.
SERVER-138094ClosedFixed
Prepare scaffolding for turning error as event on changestreams
Add the showErrorsAsEvents option, feature gate, and error codes- #65203
Fixed Versions
9.1.0-rc09.1.0-rc1025
JAVA-6366Needs Triage
NullPointerException in ByteBufNIO.hasRemaining from AsynchronousChannelStream write completion after the buffer was released
h3. Summary
A write completion handler in {{AsynchronousChannelStream.pipeOneBuffer}} calls {{byteBuffer.hasRemaining()}} after the buffer has been released. {{ByteBufNIO.release()}} sets {{buf = null}} when the reference count reaches zero, so the call throws a NullPointerException on the channel group thread. The handler is the root completion handler, so the exception is uncaught and the outer handler is never completed.
Driver: mongodb-driver-reactivestreams 5.6.5 (same code in 5.14.0)
Components
Reactive Streams
Affected Versions
5.6.5
CSHARP-6280ClosedDone
Memory-exhaustion denial of service via unbounded symbol interning during BSON/JSON deserialization (backport to main)
Fixed Versions
4.0.0
GODRIVER-2249CanceledWon't Do
Create a testing story for application devs who use the Go Driver
Previously, we have addressed requests to improve testability of applications that use the Go Driver in an ad-hoc manner. We should try to define a complete set of testing use cases and come up with a story for how we intend to support (or why we won't support) each one of them.
Original description:
{quote}
Requests to convert our main API types ({{Collection}}, {{Database}}, {{Client}}, etc.) to interfaces instead of basic structs are continuing to come in. It's clear that users desire a
Components
Testing
SERVER-138744ClosedFixed
Improve operationResponseMaxMS handling
This change refines the {{internalOperationResponseMaxMS}} soft- interruption behavior in {{PlanExecutorImpl}} so that a change stream {{getMore}} command only returns a synthetic early EOF after the scan has actually attempted work, and so an already-fired interruption is always honored.
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-36681ClosedFixed
Dotted path {$ne: null} against array of scalars returns incorrect results
{$ne: null} has some counterintuitive behavior which has hurt us several times now:
That is, \{$ne: null} doesn't necessarily return a subset of the things that \{$exists: true} returns.
This ticket is to fix incorrect logic in matcher path to fix this.
-This ticket is to track the work of changing the meaning of \{$ne: null}.-
Components
Querying
Fixed Versions
9.1.0-rc09.0.0-rc19.0.19.1.0-rc1022