Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
CSHARP-4715ClosedWon't Fix
Prevent conflating operation timeout with connection establishment timeout
This ticket was split from {{DRIVERS-2347}}, please see that ticket for a detailed description.
Components
CMAPCSOT
JAVA-5069ClosedWon't Fix
Prevent conflating operation timeout with connection establishment timeout
This ticket was split from {{DRIVERS-2347}}, please see that ticket for a detailed description.
Components
CMAPCSOT
NODE-5451ClosedWon't Fix
Prevent conflating operation timeout with connection establishment timeout
This ticket was split from {{DRIVERS-2347}}, please see that ticket for a detailed description.
Components
CMAPCSOT
PYTHON-3834ClosedWon't Fix
Prevent conflating operation timeout with connection establishment timeout
This ticket was split from {{DRIVERS-2347}}, please see that ticket for a detailed description.
Components
CMAPCSOT
NODE-5780ClosedWon't Fix
Update Timeouts to use CSOT in OIDC Machine Callback
The OIDC Machine Callbacks spec states that the timeout logic for aborting the callbacks must follow CSOT timeout logic specified as min(remaining connectTimeoutMS, remaining timeoutMS).
Once CSOT is finished we need to loop back to OIDC and update the abort logic in the callbacks.
AC:
- Update the machine callback abort signal to use the CSOT TimeoutController with a timeout of min(remaining connectTimeoutMS, remaining timeoutMS)
Components
AuthenticationCSOT
CSHARP-5683ClosedWon't Fix
Change CSOT default cursor timeout mode to ITERATION
The CSOT spec requires both applying client-side timeouts via a language-specific timeout mechanism and applying server-side timeouts by sending {{maxTimeMS}} with commands. The spec [suggests|https://github.com/mongodb/specifications/blob/master/source/client-side-operations-timeout/client-side-operations-timeout.rst#maxtimems-accounts-for-server-rtt] that a primary purpose for sending {{maxTimeMS}} is to prevent connection churn:
{quote}When constructing a command, drivers use the timeoutMS o
SERVER-138336Needs Scheduling
Convert most MONGO_UNREACHABLE in SBE to MONGO_UNREACHABLE_TASSERT
We've been migrating from shutting down the process in case of failures to aborting the queries running instead. We did this for some assertions, but there are still cases in SBE code that use MONGO_UNREACHABLE, such as in [getRawStringView|https://github.com/10gen/mongo/blob/2bf857c7fdb919e10fd9c9de2b1df63d3f4f1a15/src/mongo/db/exec/sbe/values/value.h#L1841].
SERVER-138335Needs Scheduling
Golden shape test harness for serverStatus backwards compatibility
h2. Overview
Build the golden test framework that runs an identical workload against a last\-LTS binary and a current\-tree binary and asserts the parent's serverStatus output is shape\-compatible with the current output \(epic SPM\-4962\).
h2. Scope of Work
\* Provisioning: {{buildscripts/metrics\_golden/provision\_last\_lts.sh}} \(resolve last LTS via multiversion config, symlink binaries under {{metrics\-golden\-last\-lts}}\), a new {{metrics\_golden\_shape}} Evergreen task, and a {{metrics\
SERVER-138334Needs Scheduling
Rendering: OTel bindings and serverStatus BSON export
h2. Overview
Implement the bind and render paths of the unified metrics framework \(epic SPM\-4962\).
h2. Scope of Work
\* Bind path: {{MetricsRegistryTraits::bind\(registry, svc, stats, path\)}} with typed per\-kind bind calls \({{bindCounter}}, {{bindGauge}}, {{bindHistogram}}, etc.\).
\* Instrument naming: {{mongodb.serverStatus..}} unless overridden by {{otel\_name}}. Map the IDL {{unit:}} to {{MetricUnit}} and thread {{description}} into the instrument.
\* Startup backfill: at bind time, o
SERVER-134970ClosedFixed
Disable featureFlagChangeStreamOptimizedUpdateLookup
Temporarily disable the IFR flag {{featureFlagChangeStreamOptimizedUpdateLookup}} in 9.0.2 to avoid a {{getMore}} failure affecting {{updateLookup}} change streams on sharded clusters.
On a sharded cluster, an {{updateLookup}} change stream watching a collection in a database that exists only in a shard's local catalog (no {{config.databases}} entry, e.g. mongot's {{__mdb_internal_search}} materialized-view database, used for {{$vectorSearch}} auto-embedding) aborts its {{getMore}} with {{Nam
Fixed Versions
9.0.2
SERVER-136162ClosedFixed
Disable ListIndexesAlwaysIncludesSimpleCollation feature flag
h2. *Impact*
Since SERVER-89953, on FCV 9.0+, listIndexes includes collation: \{ locale: 'simple' } on all the indexes without an explicit collation.
This causes mongoose’s [Model.syncIndexes|https://mongoosejs.com/docs/api/model.html#Model.syncIndexes()] function to always drop and re-create the collection indexes, even if the expected indexes are already built. This happens since the collation field added by SERVER-89953 makes Mongoose's diff logic consider the built index doesn't match
Affected Versions
9.1.0-rc09.0.0
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.4
SERVER-135206ClosedFixed
$convert to binData fails on a document of exactly BSONObjMaxUserSize because RCString rejects the boundary size
h2. Problem
A document whose BSON size is exactly {{BSONObjMaxUserSize}} (16777216 bytes) is a legal stored document, but it cannot be materialized as a {{Value}} of type BinData, because {{RCString::create()}} uses a *strict* {{<}} against {{BSONObjMaxUserSize}}:
BinData values are stored through this path ({{value_internal.h:283}}), so {{$convert: {input: "$$ROOT", to: "binData"}}} on a maximally-sized document fails with:
The two boundary conventions disagree: documents are valid *at*
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.7
SERVER-135360ClosedFixed
--fork makes crashes in logging subsystem invisible
When we crash in the logging subsystem, we don't send crash logs back through that same subsystem. Instead, we write them directly to stderr (see {{logNoRecursion}} and {{printStackTraceNoRecursion}} in {{{}signal_handlers_synchronous.cpp){}}}.
When we start the server with {{{}--fork{}}}, we connect stdin/stderr/stdout to /dev/null (see {{forkServer()}} in {{{}initialize_server_global_state.cpp{}}}). So, these failures go nowere. We might say "we get a coredump, isn't that good enough" but w
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137478ClosedFixed
Allow for reparse and relax internal field check in AccumulatorInternalConstructStats
Fixed Versions
9.1.0-rc09.1.0-rc1025
CSHARP-6259ClosedWon't Do
Update libmongocrypt to 1.21.0
Update [MongoDB.Driver.Encryption|https://www.nuget.org/packages/MongoDB.Driver.Encryption/] to bundle libmongocrypt 1.21.0.
NODE-6893ClosedFixed
Allow index options to pass through the driver unaltered, to be validated directly by the server
h3. Use Case
As a... Mongodb user
I want... a single source of truth in options validation
So that... I can bring my database use to any driver and get the same outcome,
...and so that I can get the latest features without waiting for driver implementation
h3. User Experience
The Node.js driver supports passing through all index options.
h3. Dependencies
This was first raised as a request for 2d sphere index options support in mongosh, see MONGOSH-2152.
h3. Risks/Unknowns
* _
Components
Index Management
Fixed Versions
7.8.0
SERVER-137074ClosedFixed
Consolidate path arrayness fuzztest cases to reduce long runtime tail
Right now every FUZZ_TEST is run for 1 hour, and tests in the same file are run serially. The path arrayness tests are the only ones with 3 tests in 1 file, so they add a 1hr tail to the libfuzzertests target ([example](https://spruce.corp.mongodb.com/task/mongodb_mongo_master_rhel8_debug_aubsan_lite_fuzzer_arm64_display_libfuzzertests!_9b998d83a7db7c0d0dc5aaced57c259e75235985_26_10_13_00_28_43/tests?execution=0&page=0&sorts=STATUS%3AASC%3BDURATION%3ADESC)). Since the tests all use the same inpu
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-102375ClosedDuplicate
Remove Feature Flag for SPM-4134
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.
SERVER-136472ClosedFixed
Create fuzztest utility that generates nested documents
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136256ClosedFixed
Create fuzzer test suite for SBE group stages
Fixed Versions
9.1.0-rc09.1.0-rc1025