Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139185ClosedFixed
v7.0 lint-pylinters task fails for unchanged files
Components
Testing Infrastructure
Fixed Versions
7.0.50
SERVER-96874ClosedFixed
Replication recovery can crash due to concurrent shutdown
In the linked AF ticket, the node was [applying oplog entries|https://github.com/10gen/mongo/blob/09d253d066bb41ef298ac79ec581ccee3bfc250c/src/mongo/db/repl/replication_recovery.cpp#L792-L811] as part of replication recovery as a standalone. There was a concurrent shutdown triggered by a SIGTERM and then the node [crashed|https://github.com/10gen/mongo/blob/09d253d066bb41ef298ac79ec581ccee3bfc250c/src/mongo/db/repl/replication_recovery.cpp#L534-L536] since shutdown [kills all operations|https://
Fixed Versions
9.0.0-rc08.3.98.0.377.0.50
SERVER-139334In Code Review
Fix Python dependency compatibility in v7.0 package tests
h2. Problem
The {{test_packages}} task on {{mongodb-mongo-v7.0-staging}} fails during Python dependency installation. The task uses Python 3.9, but the pinned {{types-PyYAML==6.0.12.20261103}} release requires Python >= 3.10.
This prevents package tests from running on multiple v7.0 build variants. See [BF-47214|https://jira.mongodb.org/browse/BF-47214] and the [failing suse12 task|https://spruce.mongodb.com/task/mongodb_mongo_v7.0_staging_suse12_test_packages_d481c335222d9536640aff825ac47da2
Fixed Versions
7.0.50
SERVER-133629In Progress
Enable Windows hermetic cross-compilation and RBE
h2. Overview
Deliver Milestone 2 of the hermetic RBE container project: enable Windows and macOS builds to use Linux-hosted hermetic containers for cross-compilation and remote execution.
h2. Parent Scope
* Epic: [DEVPROD-33617|https://jira.mongodb.org/browse/DEVPROD-33617]
* Milestone: Windows/macOS containerized cross-compilation and RBE
* Estimate: 3 engineering weeks
h2. Motivation
Windows and macOS currently depend on platform-specific build hosts and host-installed toolchains. Moving the
SERVER-137753In Code Review
Add a kill-switch server parameter for WiredTiger blind remove
h3. Background
Design: [WRITING-39975|https://jira.mongodb.org/browse/WRITING-39975]. Epic: [SPM-4886|https://jira.mongodb.org/browse/SPM-4886].
The server needs an emergency brake before it starts setting {{blind_remove}} on cursors. wiredTigerBlindWriteRatio no longer controls deletes because its code was removed in WT-18390.
h3. Change
* Add an on/off server parameter that decides whether the server sets {{blind_remove}} at all. When off, every delete works the old way.
* Set at startup, wi
SERVER-138549Open
Ensure batched ixscan fetch QSN isn't generated for timeseries bounded sort queries
SERVER-139149ClosedFixed
Try to remove skip and/or limit restrictions in batched ixscan+fetch rewrite
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139532Needs Scheduling
Complete TODO listed in SERVER-135371
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/pipeline/document_source_query_stats_test.cpp:201
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-135371&type=Code
The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this ticket to repre
SERVER-139531Needs Scheduling
Complete TODO listed in SERVER-134367
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/exec/sbe/stages/virtual_scan.cpp:75
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-134367&type=Code
The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this ticket to represent the work
SERVER-139530Needs Scheduling
Complete TODO listed in SERVER-125570
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* jstests/noPassthrough/query/queryStats/query_stats_top_k_sort_optimization.js:163
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-125570&type=Code
The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of t
SERVER-136764In Code Review
Complete TODO listed in SERVER-117943
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/modules/atlas/src/disagg_storage/pali/pali_callbacks.cpp:37
* src/mongo/db/modules/atlas/src/disagg_storage/pali/pali_callbacks.cpp:168
* src/mongo/db/modules/atlas/src/disagg_storage/pali/pali_callbacks.cpp:363
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-117943&type=Code
The next steps for this ticket are to
NODE-7953ClosedDone
Document that cursors do not support overlapping hasNext() / next() / tryNext() calls
h3. Use Case
As a developer using the Node driver,
I want the cursor API docs to say that overlapping {{hasNext()}} / {{next()}} / {{tryNext()}} calls are not supported,
So that I don't fire several unawaited calls on one cursor and get duplicate {{find}} commands, leaked server cursors or session errors.
h3. User Experience
The {{AbstractCursor}} class comment, and the comments on {{{}hasNext(){}}}, {{next()}} and {{{}tryNext(){}}}, state that calls must not overlap.
Background in N
Components
CursorsDocs
Fixed Versions
7.9.1
SERVER-137761In Progress
Run WiredTiger's verify with verify_internals config for modal validation
Full validation calls WiredTiger verify once per table and per index, and each call used to re-scan the entire metadata for duplicate btree IDs. WiredTiger now gates that database-wide check behind an opt-in verify_internals config, so the server can this separately from WT verify. This ticket adds that single call to the validate path, it will be one extra verify call (verify("database:")) before looping through verify for each collections.
Full validation calls WiredTiger verify once per ta
SERVER-136313Investigating
Add validation that a node never sends a heartbeat to itself in DSC
SERVER-134162 fixed a bug where a DSC primary's skip-self check in {{_startHeartbeats()}} compared each member's {{_id}} to the node's array index in the config, assuming that the member's ID and index position would match. After a reconfig reordered the members, the primary skipped the other electable node and heartbeated itself instead. This ocurred silently, as a node that heartbeats itself gets a well-formed response back, so the heartbeat chain keeps running and the bug is invisible from in
CSHARP-6309Investigating
[Microsoft Agent Framework] .NET: code review and NuGet release
*Background*
[mongodb-developer/ms-agent-framework-mongodb|https://github.com/mongodb-developer/ms-agent-framework-mongodb] is our MongoDB integration for Microsoft Agent Framework. It has a Python package and a .NET package, {{{}MongoDB.AgentFramework{}}}. We want the .NET package ready to ship, and we need the .NET team's help to get it there. Part of the MAF epic PENGINT-57.
*Scope*
# *Code review:* review the .NET code on {{main}} and flag anything that should be fixed or tightened b
SERVER-139528In Code Review
Add the recipient kAwaitingFetchTimestamp -> kCreatingCollection transition validator (resharding recipient pre/post-condition validations)
SERVER-139053In Code Review
Load-shedding sweep reads another thread's QueryLifespan slot without synchronization
Item 1 of SERVER-138793. {{sweepQueuedOperationsForMemoryPressure}} ({{query_memory_load_shedding.cpp:475}}) runs on the monitor thread. For each client it takes the {{ClientLock}}, then calls {{QueryLifespan::getIfExists(opCtx)}} (line 504) and {{getOpState(opCtx)}} (line 507). Both read the lifespan slot, a plain {{std::shared_ptr}} decoration on the {{OperationContext}}.
The op's own thread writes that slot without the {{ClientLock}}: {{QueryLifespan::get()}} (lazy create), {{bind()}}, and t
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139493ClosedWon't Do
CBR limit propagation floors child limit shares, costing OR/AND subtrees as free under small limits
h2. Summary
{{CardinalityEstimator::propagateLimit}} ({{src/mongo/db/query/compiler/optimizer/cost_based_ranker/cardinality_estimator.cpp}}) splits a limit between the children of OR, AND_HASH, AND_SORTED and SORT_MERGE in proportion to their cardinality estimates, and passes a FETCH's limit on to its child. Both use {{CardinalityEstimate::toCount()}}, which floors:
Any child whose proportional share is below one row is therefore given a limit of 0. That sets its output estimate to 0 and scales
SERVER-137809Open
Split insert/delete opcounters by tier: cold insert and cold delete operation metrics
[Metric support sheet for cold collection|https://docs.google.com/spreadsheets/d/1nqLitHW0S62oZzTjKMhj1G4iE9K6E2PHsqe6pqbuAJ0/edit?gid=1093816893#gid=1093816893]
Atlas needs insert/delete throughput charts for cold collections (e.g. on the Metrics tab, alongside the existing Opcounters charts). mongod already exposes insert/delete operation counters via {{{}serverStatus.opcounters{}}}, but they are tier-blind: an insert or delete against a cold collection is indistinguishable from one against
SERVER-139302ClosedFixed
Fastcount can drift on index build attempts collection on clean shutdown
If a _clean_ shutdown and restart rolls back a commitIndexBuild or abortIndexBuild the sizeStorer's count for local.config.indexBuilds is left 1 higher than it should be. At the time of shutdown, (assuming no other index builds) the collection is empty and the count is correctly 0. On startup, the index build is restarted due to that the commit/abort has been rolled back, which creates a ledger document and sets the count to 1. Oplog replay then reapplies the commit/abort, which deletes the docu
Fixed Versions
9.1.0-rc09.1.0-rc1026