Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-125415Backlog
Investigate TPC-H plan quality when data does not fit in cache
For our current TPC-H Locust workloads, the cost model always assumes that all data is in cache, and we thus end up in case 1 of Mackert-Lohman to estimate the number of random IOs.
We should see the effect of reducing the WT cache size on plan quality & stability. If this provides significantly different results, we should consider making an actual automated variant with this smaller cache size.
SERVER-138512Needs Scheduling
Support parallel plans for QuerySolutions with an 'extension'
After SERVER-137970, parallel plans may have a serial suffix however there still cannot be "extensions". This includes any sort of group or pushed down SBE node. This ticket tracks enabling such nodes to exist in the serial suffix but not parallelized yet. Note that streaming group should be explicitly disallowed.
SERVER-136964In Code Review
Consider expanding conditions where we fall back to LIS if FCBIS fails
Currently, we only check the return status of the [last FCBIS attempt and fall back to logical if it returned InvalidSyncSource|https://github.com/mongodb/mongo/blob/545e514bff2b75a7dfef8f5ba7525c3a46f83abb/src/mongo/db/repl/replication_coordinator_impl.cpp#L905]. However, if we did select a sync source but that sync source failed FCBIS for another reason such as [being unable to open the backup cursor|https://github.com/10gen/mongo/blob/dea37daf08a59d1f88077c8815b03b5b780a95f3/src/mongo/db/modu
SERVER-139035In Code Review
Add ability to write IDL extensions
h2. Motivation
The IDL compiler is a fixed three-stage pipeline (parse, bind, generate) with every grammar hard-coded into its core. Adding a new top-level grammar today means editing the block dispatch in parser.py, the spec and symbol table, the binder, and the generator, and each grammar's logic ends up spread across files it does not own.
The unified metrics framework work (SPM-4962) requires adding a grammar for metrics. asked whether it could be implemented as an extension to IDL t
SERVER-139210Needs Scheduling
Enforce metric name governance in the IDL compiler (mongodb. prefix, component rules, OTel instrument names)
h2. Overview
The design \(SPM\-4962, Build\-time validation, "Name governance"\) calls for a path\-scoped validator that enforces a unified naming convention on every instrument, since metrics are defined by different teams.
SERVER\-138594 restructured the metrics grammar validation into a single pass over the bound metrics tree \({{buildscripts/idl/idl/metrics/validators.py}}\): {{validate\_metrics}} runs {{NODE\_VALIDATORS}} against every leaf with its dotted path, which is the extension poi
SERVER-138594In Code Review
Metrics grammar binder validation in the IDL compiler
h2. Overview
Binder validation for the metrics grammar (epic SPM-4962, split from SERVER-138331). Depends on SERVER-138593.
h3. Scope
* {{buildscripts/idl/idl/metrics/binder.py}} and hooks in {{idl/binder.py}}; {{idl/compiler.py}} now calls {{binder.bind(spec, input_file)}}. All error modules land with SERVER-138593.
h3. Validation
* kind/cpp_type compatibility matrix and the unit enum.
* {{buckets}} required for histogram kinds, forbidden elsewhere; boundaries are integers in the signed 64
SERVER-138413ClosedFixed
Update registerStageStubParsers for non-IFR flags
SERVER-137483 changed registerFallbackParser to accept binary-compatible flags. registerStageStubParsers still only calls IncrementalRolloutFeatureFlag::findByName, and there is no by-name lookup for binary flags.
Fixed Versions
9.1.0-rc09.1.0-rc1026
NODE-7848Needs Verification
Node driver's autoSelectFamily default of true makes Node's process-level opt-out unreachable
*Question:* is it intended that the Node driver's {{autoSelectFamily}} default of {{true}}
makes Node's process-level opt-out unreachable for MongoDB sockets?
h2. Expected
Node exposes a process-wide default for Happy Eyeballs, settable three documented ways:
* {{--no-network-family-autoselection}}
* {{NODE_OPTIONS="--no-network-family-autoselection"}}
* {{net.setDefaultAutoSelectFamily(false)}}
We expected a {{MongoClient}} constructed without an explicit {{autoSelectFamily}} opti
Components
Networking
Affected Versions
7.6.0
NODE-6982Backlog
Flaky: Driver can successfully create and list search indexes [4]
Components
Flaky Test
SERVER-110364ClosedFixed
Resharding data replication should not restart cloner when rebuilt after a failover while building indexes
The data replication class takes in a parameter called cloningDone to indicate whether or not to restart the cloners after failovers. Currently, the cloningDone is set to true only when [recipient is in a phase > kBuildingIndex|https://github.com/10gen/mongo/blob/0fdbb0d9e4564bdca71d71c0ede460bf8b0afebe/src/mongo/db/s/resharding/resharding_recipient_service.cpp#L948]. This parameter should be set to false when rebuilding the data replication object during building index because reaching that pha
Fixed Versions
8.3.0-rc0
SERVER-138901ClosedDone
Don't run buildscripts_test on ppc64le/s390x
Addressing BF-47130
No need to run tests on platforms that don't support the codeowners.
Components
buildscripts
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139012ClosedDone
Don't schedule streams benchmark tasks on generic benchmark variants
Fixes BF-47134.
*Problem:* {{benchmarks_streams_function_stage}} fails 100% on {{enterprise-rhel-8-benchmarks}} and {{rhel8-arm64-debug-aubsan-benchmarks}} with {{Error: Received HTTP status 422}} in {{send benchmark results}}.
*Root cause:* {{streams_*_bm}} targets are only compatible with {{--streams_release_build=True}}, which the {{.benchmarks}} variants don't set. The new per-benchmark streams tasks (added in SERVER-138556) carry the {{benchmarks}} tag, so those variants schedule them. Th
Components
Build
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139030ClosedDone
Support community images from Evergreen package tasks in release-container
Add support for building community images from evg tasks
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-127705ClosedFixed
Write an output parser to get offline validation results into sys-perf reporting
Fixed Versions
9.1.0-rc0
SERVER-138175ClosedFixed
Fix use-after-free in CatchupState::abort() reentrancy via _catchupState
Fixed Versions
6.0.305.0.354.4.329.1.0-rc08.3.169.0.78.0.377.0.489.1.0-rc1026
SERVER-127585ClosedFixed
Create DSI harness to run validation
In order to properly measure performance improvements in offline validation, a workload shall be created to measure the existing performance which can be used to monitor improvements and regressions as subsequent tickets targeting validation seek to parallelize the workload.
Fixed Versions
9.1.0-rc0
SERVER-138923ClosedFixed
Complete TODO listed in SERVER-138586
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/modules/atlas/jstests/disagg_storage/checkpoint_validation_steady_state.js:242
* src/mongo/db/modules/atlas/jstests/disagg_storage/checkpoint_validation_steady_state.js:373
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-138586&type=Code
The next steps for this ticket are to either remove the outdated TODO or foll
Fixed Versions
9.1.0-rc09.1.0-rc1026