Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-135164ClosedFixed
Expand the logging in chunk migration
Expand the logging in chunk migration from SERVER-134991 to be more verbose
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.9
SERVER-135935ClosedFixed
Enable causal consistency on sharding/stepdown/multirouter suites
In a multi-router scenario, with step-ups/step-downs, a test running with maybCausalConsistency can fail to read what it had just written.
Enabling causal consistency on the affected suites will solve the issue.
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.9
SERVER-134946ClosedFixed
Spurious JSInterpreterFailure "Out of memory"
Server-side JavaScript fails with {{JSInterpreterFailure}} "Out of memory" while the actual SpiderMonkey heap is nearly empty. MongoDB's JS memory counter ({{{}mongo::sm::malloc_bytes{}}}) is incremented when a {{mozilla::StringBuffer}} is allocated but never decremented when it is released, so it tracks cumulative string allocation instead of live memory. Once it crosses {{internalQueryJavaScriptHeapSizeLimitMB}} (default 100MB) the operation is killed.
Affected Versions
8.0.32
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.9
SERVER-130823ClosedFixed
Change stream with update lookup can trip server assertion
We have a test in the mongosync codebase that sometimes (extremely rarely) trips an assertion in the server. The test opens a change stream with {{fullDocument: updateLookup}}, updates some documents in a collection, then drops that collection.
Sometimes in CI this test fails because the change stream trips a tassert in the server, with an error like:
This seems like a bug in the express engine: it seems like it shouldn't be possible to observer a state where a collection exists but do
Components
Change streams
Affected Versions
8.0.24
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.9
SERVER-136520ClosedFixed
Stage with kAllShardHosts followed by kTargetedShards without mergeShardId triggers 8596500
The tassert is triggered when a stage which sets HostTypeRequirement::kAllShardHosts is followed by a stage with which requires a shard but which does not set mergeShardId, such as $unionWith (kTargetedShards) or $group with allowDiskUse=true which disqualifies the mongos.
We also need to have no collation on the command and the collection to be untracked.
The following fail:
[\{$planCacheStats: {allHosts: true}}, $unionWith: \{...}]
[\{$planCacheStats: {allHosts: true}}, $group: \{.
Components
Distributed Query Planning
Affected Versions
9.0.28.3.118.0.328.0.34
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-133742ClosedFixed
Pause auto-compaction on all RS nodes when replica set write block is enabled and allowDeletion is set to false
{{autoCompact}} is node-local and [allowed on secondaries|https://github.com/mongodb/mongo/blob/6c5904e6ab186485e0fc9ec8ee1993cb5cc18342/src/mongo/db/commands/auto_compact.cpp#L139-L141]. Replica set write blocking only [pauses|https://github.com/mongodb/mongo/blob/6c5904e6ab186485e0fc9ec8ee1993cb5cc18342/src/mongo/db/topology/user_write_block/writes_recoverable_critical_section_service.cpp#L583-L586] it in the {{blockReplicaSetWrites}} command path, which is [primary-only|https://github.com/mon
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-136977ClosedDone
Surface info-level hook logs more clearly in GenerateAndCheckPerfResults (benchmarks_sep)
Update the logging in GenerateAndCheckPerfResults so that its important info-level messages are easier to find in Evergreen. Currently, some hook logs appear only in the merged job0/all log and are missing from the test-specific logs shown in the Tests tab, making them difficult to discover.
Where practical, run the relevant hook logic through CheckPerfResultTestCase so its logs are associated with the test and surfaced in the test-specific output. Preserve useful info-level messages and make
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-136798ClosedFixed
startAfter fails with NoMatchingDocument on the resume-token event: the "required" pre-image check is applied to the event the stream must start after
With {{fullDocumentBeforeChange: "required"}} (or {{fullDocument: "required"}}), a stream resumed with {{startAfter}} or {{resumeAfter}} applies the "required" check to the event the resume token points to. That event must not be read at all: the stream is supposed to continue after it, and it is never returned to the client.
If that event is an update, replace or delete made before pre-images were enabled, the aggregate fails with {{NoMatchingDocument}} (47) before returning anything, althou
Affected Versions
8.0.267.0.37
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-137449ClosedFixed
Add a test that tests the resumability of wildcard indexes on all phases of an index build with keys that have the same multikey metadata keys
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-137644ClosedFixed
Remove blocking thresholds for BM_AGG_MATCH_ONE
Fixed Versions
9.1.0-rc10259.0.9
SERVER-137170ClosedFixed
Timeseries search-index ban bypass via view resolution in search index commands
A user can get around the rule that forbids search index commands on time-series collections by creating the search index against a view over the collection instead of the collection itself. The server then forwards the index request with the time-series collection's real UUID to the search index management endpoint.
Fixed Versions
9.1.0-rc09.0.9
SERVER-137505ClosedFixed
Capture and verify production compiler and linker versions
Capture compiler and linker versions in build provenance and verify production releases against `toolchain_versions.json`, using shared platform pins for native and cross builds. `test_packages` independently rechecks recorded versions; published packages skip current pins.
Separate Bazel probes support Clang, GCC, LLD, gold, BFD, and mold, including IBM and macOS cross execution. Capture never executes target servers. Evergreen uploads captures for development and production configurations and
Components
Bazel
Fixed Versions
9.0.9
SERVER-135868ClosedFixed
Define a single global clang version for all Bazel toolchains and verify it with a --version check
h3. Context
Follow-up from review of [SERVER-135723 PR|https://github.com/10gen/mongo/pull/63462#discussion_r4126326352].
The server now pins clang versions separately per toolchain:
* Native macOS: {{_LLVM_VERSION = "19.1.7"}} in {{bazel/toolchains/cc/mongo_apple/mongo_apple_toolchain.bzl}}
* Linux: the v5 toolchain archives in {{bazel/toolchains/cc/mongo_linux/mongo_toolchain_version_v5.bzl}}. The version there is defined by the toolchain builder, not the server, and may not exactly match wha
Fixed Versions
9.0.9
SERVER-132727ClosedFixed
agg_lookup_and_move_primary.js should be resilient to conflictingOperationInProgress
The agg_lookup_and_move_primary test runs movePrimary as one of the stages. This test runs in config transition and add/remove shard suites, where movePrimary can also be issued by background hooks. When running in these suites, the test should accept conflicting operation in progress errors.
Fixed Versions
9.1.0-rc09.0.9
SERVER-137527ClosedFixed
Reorder timeseries verification checks
Verify first that the collection is a [valid timeseries |https://github.com/10gen/mongo/blob/3c283495766841588d28dba95c70bf8382f7507a/src/mongo/db/shard_role/shard_catalog/database_impl.cpp#L1002-L1007]. Assert [viewlessTimeseries|https://github.com/10gen/mongo/blob/3c283495766841588d28dba95c70bf8382f7507a/src/mongo/db/shard_role/shard_catalog/database_impl.cpp#L1002-L1007] afterwards.
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-133321ClosedFixed
$lookup on a view definition with extension $search stage binds the view into its own $_internalSearchIdLookup w/ different behavior on topology
h1. Summary
When \{{$lookup.from}} is a view whose pipeline desugars to a mongot-style source stage plus \{{$_internalSearchIdLookup}}, the foreign-view binding step binds the view's *own* pipeline onto that idLookup stage. On an unsharded deployment idLookup then prepends \{{$match: <documentKey>}} to the bound view pipeline, displacing the \{{PositionRequirement::kFirst}} source stage, and the query fails with:
On a sharded cluster the same query succeeds. \{{$unionWith}} and \{{$gra
Fixed Versions
9.1.0-rc09.1.0-rc10229.0.9
SERVER-137093ClosedFixed
Exclude change_stream_update_lookup_too_many_matching_documents.js from sharding_csrs_continuous_config_stepdown
The suite steps down the config server primary every 8 seconds. The test calls waitForClusterTime, which runs _configsvrGetHistoricalPlacement against the config primary (jstests/libs/query/change_stream_util.js:1509). If the call lands during a stepdown, the command returns an error with no historicalPlacement field. The helper then throws can't access property "status", ... historicalPlacement is undefined.
Fixed Versions
9.1.0-rc09.0.9
SERVER-132152ClosedFixed
Make resharding_coordinator_service_test.cpp skip calling make*ProceedToDone
in runReshardingAbortWithoutQuiescingBeforeFailover
Fixed Versions
9.1.0-rc09.0.9
SERVER-134249ClosedFixed
Skip serializing internal hybrid search field when serializing for query stats
Fixed Versions
9.1.0-rc09.1.0-rc10229.0.9
SERVER-138311ClosedFixed
Make ValidateOptions Plain-old-data
Validate options maintains no class invariant and requiring the constructor prevents effective use of designated initializers.
Fixed Versions
9.1.0-rc09.1.0-rc1025