Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138463In Progress
Move IBM crypt builds to ARM64-hosted cross compilation
h2. Overview
Extend the IBM cross-compilation work in DEVPROD-43701 to the crypt build pipeline for Z Series (s390x) and Power (PPC64LE). Move crypt compilation and linking to dynamically allocated ARM64 Linux hosts using the cross-build approach already used for server builds.
h2. Scope
* Audit the IBM crypt build variants and tasks, including {{crypt_create_lib}}, for compilation, linking, and packaging that still depend on native IBM hosts.
* Reuse the appropriate cross toolchains and target
Components
Build
Fixed Versions
9.0.98.3.18
SERVER-138484ClosedFixed
Always report QMLS counters in serverStatus, even when load shedding is disabled
{{serverStatus().queryMemory.loadShedding}} is omitted whenever load shedding is disabled ({{{}queryMemoryLoadSheddingLowMarkPercent{}}} = -1), because of the early return in {{{}appendQueryMemoryLoadSheddingStats(){}}}. Mongotune switches shedding on and off over time, so consumers see gaps in the cumulative {{operationsShed}} / {{idleCursorsShed}} / {{idleCursorBytesShed}} counters.
Atlas auto-scaling (TUNE-1578) will compute a rate from {{{}operationsShed{}}}. It treats missing samples as
Components
DiagnosticsQuery Execution
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-138489ClosedFixed
Robustify operationResponseMaxMs handling
This change makes the following changes to how the optional {{operationResponseMaxMs}} deadline is handled in change stream oplog scans:
* Preserve the response deadline across resources releases, i.e. when {{PlanExecutorImpl}} calls {{releaseAllAcquiredResources()}}. Otherwise the deadline may restart from its original value after resources are re-acquired.
* Also enforce the deadline while waiting for new oplog entries inside {{insert_listener::waitForInserts()}}. This makes the deadline apply
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-133069ClosedFixed
Exclude FLE2 text tests from config transition suites
`fle2_text_test_fixture.js:updateAndValidate()`'s cleanup
omits the shard key ({{{}last: "hashed"{}}}), so mongos broadcasts it to all chunk-owning shards with {{{}ChunkVersion::IGNORED{}}}. In [the failing run|https://parsley.corp.mongodb.com/test/mongodb_mongo_master_enterprise_amazon_linux2023_arm64_all_feature_flags_extra_system_deps_sharded_clusters_disagg_sharded_colls_jscore_passthrough_secondary_reads_with_balancer_3_linux_enterprise_a1054188c5ddd8b537cf19cd69af204b9f9c4bb3_26_08_05_
Fixed Versions
9.0.0-rc49.0.9
SERVER-138584ClosedFixed
Bump mongot-extension version to v2.0.10
Bump mongot-extension version to v2.0.10 to pick up $rerank memory optimization and multi geo/cloud support.
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-134126ClosedDone
Remove Copybara tasks from old branches
h2. Overview
Remove the remaining legacy Copybara synchronization implementation from the v4.4, v5.0, and v6.0 release branches.
h2. Background
Copybara synchronization is now orchestrated from the master branch. The older release branches still contain Copybara tasks that invoke {{buildscripts/sync_repo_with_copybara.py}} and depend on the removed {{app_id_copybara_syncer}} Evergreen expansion, causing failures such as [BF-46001|https://jira.mongodb.org/browse/BF-46001].
h2. Scope
* Remove
Fixed Versions
5.0.366.0.314.4.339.0.9
SERVER-132218ClosedFixed
Replace multi updates with individual updates in fle2_text_test_fixture.js
The unencrypted multi updates in fle2_text_test_fixture.js are flaky under config transitions. We already cannot perform multi updates in QE, so we should replace the existing multi updates with individual updates to avoid encountering irrelevant failures.
Components
Queryable Encryption
Fixed Versions
9.1.0-rc09.0.9
SERVER-138408ClosedFixed
Fix BlockingWrite behavior in intent registry
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-137968ClosedFixed
Add counter for execution engine used in query stats
In the future it will be more difficult to determine which queries use SBE and which use classic. Let's add a counter in query stats for which engine was used. It can be in the same place the plan shape counters are counted:
https://github.com/10gen/mongo/blob/aeb839c4b21a0d5b845cebf31258582946ee5d57/src/mongo/db/query/get_executor_deferred_engine_choice_lowering.cpp#L69-L82
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-138808ClosedFixed
Update rules_nodejs version
Fixed Versions
8.0 Required8.3 Required9.1.0-rc09.1.0-rc10259.0.9
SERVER-138810In Code Review
Fix custom build CI double applying patches
Package task will fail if you try to use a patch on a custom build because it double applies it. Fix thisx.
Fixed Versions
8.0.39
SERVER-138745ClosedFixed
Enable IBM package tests with Podman
Re-enable {{test_packages}} on all six IBM PPC64LE and s390x release variants using native Podman hosts. {{package_test_container.py}} abstracts Docker and Podman while preserving package validation, logs, and exit codes.
Reuse master’s Podman preflight with isolated runtime and storage per execution, recovering stale state automatically. Bound operations and container lifetimes; clean up containers and private registry credentials after timeouts or termination.
Add {{rhel9}} container/depende
Components
Storage
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-138882Needs Merge
Prevent resharding_recipient_buildindex_stepup_deadlock.js from running in multiversion on v8.0
Fixed Versions
8.0.39
SERVER-92716ClosedFixed
Remove dependency between the WiredTigerStats struct and WiredTiger statistics themselves.
A recent change went through, performance motivated, to make retrieving and storing WiredTiger statistic more efficient. This coupled strongly with the WiredTiger code which meant any WiredTiger session statistic changes would cause assertions to fire. The goal of this ticket is to partially revert SERVER-86387 to still maintain some of the performance changes but not have a dependency on WiredTiger.
Fixed Versions
8.1.0-rc08.0.39
SERVER-132736ClosedFixed
transaction_aborted_under_cache_pressure.js leaks sessions at teardown and the cache-pressure detector rarely fires under WT-18120's improved eviction
h2. Summary
{{jstests/noPassthrough/txns_cache_errors/transaction_aborted_under_cache_pressure.js}} has been flaky/failing on {{amazon-linux2023-arm64-static-compile}} and {{commit-queue}} since WT-18120 landed (tracked as BF-45315). Root cause is two long-standing test defects that WT-18120 pushed from rare to frequent — not a WiredTiger bug.
h3. What fails in CI
On the mainline failure the cache-pressure mechanism worked correctly ({{{}successfulKills > 0{}}}), the fill loop exited norm
Components
Testing Infrastructure
Fixed Versions
9.1.0-rc09.0.48.3.18
SERVER-133912ClosedFixed
fcbis_restart_node_during_sync_with_pre_images.js doesn't kill backup cursors
Note that for initial sync to succeed, the initial sync node needs to create a backup cursor on the primary, which requires any backup cursors _already_ on the primary are killed.
In SERVER-127978, we changed the failpoint that the initial sync node waited on.
We wanted to halt the initial sync node in the middle of its initial sync, but *before* it made a backup cursor, so we can kill the backup cursors on the primary first, and avoid a failed initial sync.
However, even though we [kill
Fixed Versions
9.1.0-rc09.1.0-rc10229.0.9
SERVER-138608ClosedFixed
Allow remote execution for nightly patch builds
Allow patches on {{mongodb-mongo-master-nightly}} to retain configured remote execution even when {{is_release=true}}. {{evergreen/bazel_compile.sh}} skips the local execution and cache overrides for these patches, including the toolchain provenance capture build.
Share the provenance eligibility rule between {{package_test.py}} and {{package_test_provenance.py}} so nightly release patches skip local-execution provenance creation and validation. Waterfall builds and explicit release patches in
Components
Bazel
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.9
SERVER-137019ClosedDuplicate
Make donors unpin durable history earlier
The history gets unpinned when coordinator transitions to apply. The durable history is only needed for cloning, so it is no longer needed when all recipients transition to building indexes.
NODE-7733In Progress
[Mastra] Advanced Search & Retrieval
{panel:bgColor=#fafbfc}
*What it is:* A set of production-grade retrieval features for Mastra's MongoDB integration: hybrid search that combines vector and full-text matching, Voyage rerankers to improve result relevance, automated embeddings that handle vectorization server-side, and pre-filters that work reliably at scale without hitting database limits.
*Who it's for:* Developers building RAG applications and AI agents with Mastra who use MongoDB as their vector database and retrieval bac
Components
ABX