Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-137662Investigating
Expose WT history pinning APIs
Some features such as STREAMS-2503 would benefit from being able to pin durable history in order to read large collections at a specific timestamp, we could expose the history pinning feature through an API for similar internal consumers.
SERVER-138651Backlog
Consider if "runtime settable only" server parameters make sense
Today, we can independently mark server parameters as either startup settable (via the config file, or as startup parameters to the process) or runtime settable (via the setParameter command) or both.
We have some server parameters defined today that are only settable at runtime ([example|https://github.com/10gen/mongo/blob/79377e0c536be1319cf95f0572cb06c21c324e16/src/mongo/db/modules/enterprise/src/ldap/ldap_runtime_parameters.idl#L7-L20]).
This complicates things for Atlas in the short t
PYTHON-6238ClosedWon't Do
Enable ruff BLE rules
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
Ruff 0.16.0 added the {{BLE}} category of rules derived from the flake8-blind-except linter.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Remove the suppression of {{BLE}} rules or add an explicit comment explaining why keeping it suppressed is correct.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
SERVER-118945ClosedFixed
In-order timeseries measurements spanning epoch-time are incorrectly promoted to version 3
When inserting documents into a collection with pre-epoch timestamps, inserting documents into the same bucket that are post-epoch results in a version 3 bucket despite the collection meeting the criteria for version 2.
Fixed Versions
9.0.0-rc0
SERVER-137870ClosedFixed
Remove sample size/method parameters from analyze
Remove `samplingMethod`, `sampleSize`, `numChunks` from analyze. Analyze will now only persist a default sample.
If this is done before we implement support for reusing the same sample for requests of different sizes, the temporary solution is to persist two samples, one for JOO's default and one for CBR's.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137043In Code Review
Fix non-deterministic parts of build
Some parts of our build have non-deterministic outputs. These were discovered by doing non-cached builds and hashing outputs. A futures PR will add CI checks that keep our build deterministic, but for now fix the known issues.
Components
Build
SERVER-139050Backlog
[POA] Enable startup_recovery_for_restore_crash_mid_batch.js
Currently disabled because it's hard to figure out what to do with this test that runs on ASC and DSC.
SERVER-62246ClosedWon't Do
writeConcern all
If I want write to be acknowledged when all voting nodes have confirmed a write, I have to manually specify the number of nodes in my writeConcern (e.g. "w: 3" in a 3-node set).
It would be helpful to support a "w: all" writeConcern that supports this behavior independent of replica set topology.
We already do something similar with the "votingMembers" [commitQuorum|https://docs.mongodb.com/manual/reference/method/db.collection.createIndexes/#std-label-createIndexes-method-commitQuorum] se
SERVER-137729ClosedFixed
Make collectionHash independent of validation mode
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138996Backlog
Make use of standard attribute syntax for more mongo compiler attributes
SERVER-134969Open
Remove BSONColumn content validation from kDefault in BSON validator
As per [this slack thread|https://mongodb.slack.com/archives/C0BBJE7SVPS/p1784816336262319], we agreed that moving validation of BSONColumn needs to be when parsing the BinData and creating the BSONColumn object, and in the read/write path.
*Context*: Today the BSONColumn are validated when validating a BSON object for structural issue. This has been categorized as misplaced because a valid BSON object is still valid even if it contains unparseable BSONColumn as BSONColumn is a BinData format
SERVER-139049In Code Review
Remove unread scan fields in SBE blueprint dead slot elimination
Extend SBE blueprint dead slot elimination to remove the fields of a {{scan}} stage whose slots nothing reads, behind {{featureFlagSbeBlueprintRewrites}}.
* For example, both foreign-side scans of a two-{{$lookup}} pipeline extract {{j1}} and {{j2}} for every document, though nothing reads them
* Follow-ups: unused record id slots, then the fields of multi-range scans and fetches
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-121988ClosedDone
$lookup on sharded view with concurrent drops and create matches no documents
Quick summary: $lookup doesn't handle multiple view kickbacks correctly. The repro explains one situation where multiple view kickbacks are possible.
Repro steps (also can be found in the comments):
# Run a $lookup on a sharded view as the foreign collection (view A backed by collection B).
# After the 'CommandOnShardedViewNotSupportedOnMongod' is raised and while mongos is resolving the view, we drop collection B and recreate it as view B on collection C. This can also happen between ge
SERVER-128560ClosedFixed
Audit feature flag checks that derive VersionContext from expCtx's opCtx
Filing this as a separate ticket to keep the immediate fix for AF-17643 more minimal so it can be backported easily if needed.
From 's comment in AF-17643:
{quote} - Outside of the feature flag checks in the expCtx, there are ~28 other sites in the codebase that derive the VersionContext straight from an expCtx's opCtx (from a quick sweep with Claude). These are most likely paths that expect to run with a live opCtx, but it may be worth verifying whether these could be reached from one
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139097Needs Scheduling
Remove support for Ubuntu 16.04 on April 30, 2026
Ubuntu 16.04 reached EOL on April 30, 2026.
SERVER-138409Open
Disagg primary liveness watchdog steps down a healthy primary when commit-time eviction assist stalls under cache pressure
h2. Symptoms
BF-45295: {{disagg_concurrency_simultaneous}} intermittently fails on {{enterprise-amazon-linux2023-arm64-disagg-no-feature-flags-extra-system-deps}}. The primary mongod exits abruptly with code 14 while the FSM batch is running, and the test then hangs for 600s in {{Finding primary}} before failing.
The mongod log shows the primary liveness watchdog firing:
* First interval: [log 12984004|https://github.com/10gen/mongo/blob/9d5269427e60f18b9468a3da1abbc65d0f892fdd/src/mongo/db
SERVER-139102Open
Remove multiversion handling for afterOpTime once 9.0 is not lastlts
Placeholder ticket for making a TODO
h3. Background
As part of SERVER-29729, the {{afterOpTime}} readConcern field was removed from the IDL and all internal support for it was removed. The {{afterOpTime}} field was the attack surface behind three CVEs.
h3. Problem
Several JS tests were updated to accept *both* {{ErrorCodes.IDLUnknownField}} (the new behavior, where {{afterOpTime}} is an unknown field) and {{ErrorCodes.FailedToParse}} (the last_lts / v9.0 behavior, where {{afterOpTime
SERVER-134199Open
Simplify invariant failure log ID
All kinds of invariants are outputting this log message:
But all of them have different log ID. A single log ID should be used instead.
SERVER-138592Open
Complete TODO listed in SLS-8072
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* buildscripts/modules/atlas/suites/no_passthrough_disagg_override_sharded.yml:54
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SLS-8072&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 tic
SERVER-138907Blocked
Make the waiter list map keyed by timestamp only, not opTime
Once we remove the afterOpTime read concern, we should refactor the list to use cluster times as the keys, avoiding the footgun of the opTime comparator not being totally ordered.