Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-124331Open
$persistedStats — mongod: summary mode
New aggregation stage to read persisted stats on mongod. $planCacheStats-like pattern.
This ticket should handle implementing summary mode as specified [here|https://docs.google.com/document/d/1cLItPQB02UXl3r57SkgJOLN0cksIkbGpPOuFWTMww2M/edit?tab=t.0#heading=h.75wvx26w9k6m].
SERVER-139489Backlog
Multiversion and Upgrade/Downgrade Testing
This ticket is to ensure there is adequate multiversion testing
coverage for this project.
1. Test that this feature works correctly on mixed binary version
clusters.
2. Test how the feature behaves when upgrading FCV turns the
feature on
3. Test that the correct behavior occurs when downgrading FCV
completely and then upgrading FCV completely
4. Test that the correct behavior occurs if the FCV upgrade fails.
5. Test that the correct feature behavior occurs if the FCV downgrade
fails after only
SERVER-139488Backlog
Documentation Updates
This ticket is to update all types of documentation API Guide,
Programming Guide, and Architecture Guide related to the project.
PYTHON-6279Ready for Work
Enable ruff rule W505
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
Ruff rule [W505|https://docs.astral.sh/ruff/rules/doc-line-too-long/] enforces the line length limit set by {{lint.pycodestyle.max-doc-length}}. That limit should be set to 100 for consistency with our coding standards.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Enable rule W505 and make the code (docstring) changes required to pass it.
h3. *Pitfalls*
{c
Components
Infrastructure
SERVER-137041ClosedFixed
Extend explain with parallelPlanner output
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138148ClosedGone away
Complete TODO listed in SERVER-119213
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/replicated_fast_count/replicated_fast_count_delta_utils.cpp:109
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-119213&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 t
GODRIVER-4246ClosedDone
Replace AdvanceConfigClusterTime oplog-note loop with cluster time gossip and gate on 9.0+
h3. *Name of Failure:*
TestCursor_tailableAwaitData_ShortCircuitingGetMore/maxAwaitTime_less_than_operation_timeout/watch
h3. *Link to task:*
https://parsley.corp.mongodb.com/test/mongo_go_driver_tests_windows_44_plus_zlib_zstd_support__version~4.4_os_ssl_40~windows_64_test_sharded_noauth_nossl_zstd_compression_3c254894
h3. *Context of when and why the failure occurred:*
On 9.0+ sharded clusters, opening a change stream waits until the config server has caught up to mongos' cluste
Components
Evergreen
SERVER-138310Backlog
Report nUpdateOps and nDeleteOps in query stats for bulkWrite ops
_Why:_ Query stats for update and delete ops inside a bulkWrite command report {{writes.nUpdateOps}} and {{writes.nDeleteOps}} as 0. The standalone update and delete commands set these counters to the number of statements in the command, but the bulkWrite path does not set them, so the values are inconsistent with the standalone commands.
_What:_ Decide what these counters mean for a bulkWrite op (for example 1 per op, or the number of ops of that type on the namespace) and populate them on the
SERVER-138127Open
Re-enable rid-sensitive dbHash checks in test fixtures with groupId-membership-aware opt-in
The {{includeReplicatedRecordIds}} opt-in in {{getHashesUsingSessions()}} was removed to let the {{groupId}} implementation land without mass fixture hash failures from legitimately divergent {{rid}} spaces. This ticket restores rid-sensitive hashing keyed on {{groupId}} membership instead of the per-collection catalog flag.
h2. Semantics
{{rid}} inclusion in a node's {{dbHash}} output is a function of that node's membership: in-group nodes (persisted {{groupId}} non-null) hash in-scope coll
SERVER-139484Needs Scheduling
Test coverage for large scale index builds
Current index build tests lack coverage for builds
* exceeding ~120 MB of index keys
* with more than 3 indexes in one createIndexes call
Some mechanisms are only reachable at volume and are currently only tested at toy scale: merge fan-in, sorter behavior with many spilled runs, and memory accounting across many concurrent indexes. Others such as yields, restart, rollback, initial sync, disk-space handling, have small-scale correctness coverage, but their behavior on large builds (natur
SERVER-138223Open
Clear the groupId on FCV downgrade (C2)
FCV downgrade is the clean disable for set-wide Replicated RecordIds: every node drops its groupId collection, fenced at the downgrade entry.
h2. Details
- The trigger is the transition from upgraded to downgrading, the first observable entry of the downgrade, not its completion: the primary stops emitting rids and clears its own {{groupId}} at that point, and secondaries clear when applying the entry, so the whole downgrade window is fenced.
- The clear *DROPS* the collection rather tha
SERVER-138221Open
Found the groupId at setFCV upgrade completion
Founding without an election for set-wide Replicated RecordIds: when setFCV upgrade to latest completes on a flag-on primary holding no groupId, mint one in the same WUOW as the upgrade-complete write.
h2. Details
- {{foundingOpTime}} is the setFCV upgrade-complete entry's opTime, so it is a real fencing optime in the history.
- No announcement is needed at founding: no other node can hold a groupId at that point (C2 cleared everyone at the preceding downgrade, or none ever existed).
- Rid
SERVER-139387ClosedFixed
Off-By-One error in gen_id
As part of SERVER-135417, an off-by-one error was introduced which causes generations to start on 2 instead of 1.
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-135417ClosedDone
Modify read path to refuse if no gen_id
Modify read path to refuse if no gen_id
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138110Open
Clear groupId on mismatched new-primary noop (C1), with batcher fence
Implement the C1 clear trigger for set-wide Replicated RecordIds : applying a new-primary noop whose ({{groupId}}, {{foundingOpTime}}) is absent or differs from the node's own drops the node's {{groupId}} table at the noop's timestamp.
h2. Details
- Appliers currently skip all noops without reading the payload, add inspection for the new-primary noop fields.
- The noop must be processed individually so the clear commits before any later-timestamped entry applies: change the [{{isNewPrim
SERVER-139338In Code Review
Add a monguard option to MongoRunner
Similar to SERVER-139108, we want the JS test helpers to have a monguard option to run monguard with the MongoRunner.