Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
PYTHON-6150Backlog
Add test coverage for top-level error handling in multi-batch bulkWrite
This ticket was split from {{DRIVERS-3670}}, please see that ticket for a detailed description.
Components
CRUD & Command-Level Operations
PYTHON-6257ClosedGone away
Static PR checks failing to reach ubuntu archives
h3. *Name of Failure:*
Static cppcheck and Mod WSGI latest tests.
h3. *Link to task:*
https://github.com/mongodb/mongo-python-driver/actions/runs/43055799726/job/130644793090?pr=3199 and https://github.com/mongodb/mongo-python-driver/actions/runs/43055799831/job/130659564796?pr=3199.
h3. *Context of when and why the failure occurred:*
Started occurring today, Nov 11 2026.
h3. *Stack trace:*
PYTHON-6276ClosedWon't Do
Enable ruff rule ERA001
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
Ruff's ERA001 rule forbids commented-out code. This is generally a good practice and improves codebase quality and readability.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Enable rule ERA001 and make the required changes to pass it.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
PYTHON-6233Backlog
Remove pymongocrypt version test helpers
h3. *Context*
PYTHON-5959 raises the pymongocrypt floor for PyMongo 4.20 to {{pymongocrypt>=1.21.0,<2.0.0}}. The test suite does not explicitly need version gates: tests should run against what CI installs or fail, not silently skip.
h3. *Definition of done*
- The test-side version gates are removed.
- The runtime check stays: {{check_min_pymongocrypt()}} in {{pymongo/encryption_options.py}}. It is the only guard for pip resolver bypass (an old pymongocrypt installed alongside the ne
SERVER-139346In Code Review
Add MakeObj fuzzer in preparation for makeObj fusion optimization
SERVER-136912In Code Review
TLA+ proposed changes to prevent a replaced node from affecting the majority commit point
In WRITING-40450 we came up with proposed changes in order to avoid a replaced/restarted node from going back in time and affecting the majority commit point of the replset.
Changes taken from the [decision doc|https://docs.google.com/document/d/1dGRjirN43xWQv-XlXqekWeMo77oJkc0zzSKlJhH6R2M/edit?tab=t.0#heading=h.6vzuqy1ox6ng]:
* Server changes so that a node in STARTUP2 cannot vote.
* Server changes so that initial sync (LIS or FCBIS) is not considered completed until it is caught up to t
SERVER-134248ClosedFixed
Make an error upon the xxh3 hash generated by validate and continuous validation's hash mismatch
Fixed Versions
9.1.0-rc09.1.0-rc1026
PYTHON-6275ClosedDone
Enable all ruff PERF rules
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
Only a portion of ruff's {{PERF}} linting rules are enabled by default. Enabling all of them improves performance and code consistency.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Enable the entire suite of ruff {{PERF}} linting rules and make the required changes to pass them.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What
SERVER-137887In Progress
Bound interrupt-check gaps while serializing and deserializing large $group spill partials
A single large $group spill record can take longer than the interrupt-check interval to serialize or deserialize. SERVER-136021 checks between records and merge partials; it does not bound work inside a record. SERVER-136213 adds classic spill-sort/$push checks and removes an SBE recovered-array deep copy, but large-record spans remain. These can delay killOp/maxTimeMS handling and produce interrupt-check delinquency.
SERVER-139181ClosedFixed
Move transactions task ownership to Storage Execution
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139089ClosedFixed
Transfer bulkWrite task ownership to query
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-137443In Code Review
Remove Parallel Collection Validation Feature Flag
Enable namespace level parallelism in Offline Validate by default.
SERVER-139014Blocked
Support accumulators with variable initializers in streaming group
When an accumulator has a variable initializer, we add a project to rewrite the group key into an object form, and use that as the group key slot as long as the group key is also an object. Currently we don't use streaming group in this case.
To support, need to correctly build a cluster key representation of the rewritten grouping key.
Example rewrites:
Grouping key is an object. We build an object form of the key (s6) and use that as the grouping key and the slot used by the init
SERVER-139355Needs Scheduling
Support for parallel scans when query settings/index hints are applied
Spun out from [https://github.com/10gen/mongo/pull/65920] where we conservatively bail out of parallelism on _any_ index hint being applied. At the time, this meant $natural (which arguably defines an order and thus parallelism would have to sort-merge) but once index scans are supported we should revisit this check.
SERVER-138778ClosedFixed
Add incremental spilling support to Spiller and ContainerBasedSpiller
When a primary-driven index build spills its sorter, every batch is written back to back while the collection scan is suspended, which engages flow control against concurrent user writes. Incremental spilling, one batch per call paced to the collection scan, avoids the spike, but {{Spiller::spill()}} has no way to express it.
This adds {{beginSpill()}} and {{spillIncremental()}} to the Spiller interface (the writer is created by {{beginSpill()}} and held open across {{spillIncremental()}} calls
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138666Needs Scheduling
Don't bypass removeInclusionProjectionBelowGroupRecursive for streaming group
{{removeInclusionProjectionBelowGroupRecursive}} ({{{}planner_analysis.cpp{}}}) only matches {{{}STAGE_GROUP{}}}, so it skips {{StreamingGroupNode}} ({{{}STAGE_STREAMING_GROUP{}}}) and eligible fetch plans keep a redundant projection below the group. Found by Copilot in review of [SERVER-138655|https://github.com/10gen/mongo/pull/66084/changes#top].
* Handle both stage types.
* Add a streaming-enabled variant of {{{}StreamingGroupEligibilityTest.InclusionProjectionBelowEligibleGroupIsElided{
SERVER-139350In Code Review
Search index commands on mongos ignore {ok: 0} replies from the primary shard when resolving the target namespace
In search_index_process_router.cpp, fetchCollectionUUIDAndResolveView and resolveViewHelper only check the transport status of the listCollections and _shardsvrResolveView replies, not the command status. As a result, a failed listCollections surfaces as a "wrong type for field" error instead of the shard's error, and a failed _shardsvrResolveView makes a view look like a missing collection (NamespaceNotFound).
We should check both replies with AsyncRequestsSender::Response::getEffectiveStat