Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139123ClosedFixed
Move task ownership to CAR / CS
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138010Open
Committed transactions report a spurious writeConcernError when a session kill interrupts the majority write-concern wait
A transaction that commits successfully can still report a {{{}writeConcernError{}}}(WCE) if a session kill delivered an interrupt to the committing operation before its majority write-concern wait completed. The interrupt is sticky and cannot be retracted, so the client receives {{ok: 1}} with WCE on a transaction that is durably committed. Retrying the whole operation in response is unsafe because the write already committed.
h3. Why the error is not recoverable for clients as-is?
[{{Tempo
SERVER-95324ClosedFixed
Disable chunkMigrationConcurrency
{\{chunkMigrationConcurrency}} can led to excessive resource consumption. In some instances, it also results in an increase in orphaned documents, complicating data management. For this reasons we are deprecating and removing it. Setting this parameter won't have any effect on the cluster, we are making it a no-op operation
Components
Sharding
Fixed Versions
8.1.0-rc08.0.57.0.23
SERVER-139266Needs Scheduling
Remove knob internalQuerySamplingCEMethodForPersistentSamples
Remove the query knob. Make sure that api compatibility is maintained, check with Atlas and Atlas Infinite to make sure knob is not in use anywhere what will break when it's removed.
Fixed Versions
9.1 Required
PYTHON-6262ClosedFixed
getMore retries and multi-mongos retryable writes fail in load-balanced mode
h3. *Context*
PYTHON-6167 makes the load-balancer Evergreen tasks run the whole default suite under {{loadBalanced=true}}. The first run failed 4 tests per task, and the PR now skips them in LB mode. Two underlying gaps:
* Pinned-cursor getMores never retry on {{SystemOverloadedError}} and {{RetryableError}} errors; the retryable reads and Client Backpressure specs expect retries in LB topology. Failing: {{test_retry_overload_error_getMore}} and the two {{TestClientBackpressureGetMoreRetri
Components
Load Balancer
Fixed Versions
4.20.1
SERVER-137994Open
Join optimization INLJ over multikey compound index returns duplicate row per array element
createIndexProbeQSN() in reorder_joins.cpp builds the IndexEntry with isMultikey=false regardless of the catalog, so buildIndexedJoinIndexProbe() never adds the dedup stage. Probing \{y: 1, tags: 1} with bounds [x, MinKey]..[x, MaxKey] returns the foreign document once per element of tags. The join field itself is scalar, so path arrayness does not block the plan; INLJ is chosen naturally with a large foreign collection.
SERVER-130790Backlog
Handle bumping CollectionTag/index fingerprints if multikeyness flips due to document write
As stated in SPM-3143, multikeyness flips from a document write operation are not subject to the same strict transactional guarantees as DDL operations. This means that updating the necessary versions and fields due to such an operation will require careful synchronization.
SERVER-121215Backlog
Cost of INDEX_PROBE_NODE does not take into account number of index keys visited per 1 probe
This plan is costed incorrectly:
The cost of the INDEX_PROBE_NODE is not reported but the cost of the overall join is 1.02, and the cost of the left join input is 0.92. This leaves a cost of 0.10 for the right input and the join itse
SERVER-139139ClosedFixed
Extract model-agnostic FSM walk into FsmCommandGenerator base class
Extract the randomized graph walk of {{ShardingCommandGenerator}} into a model-agnostic base class, so a transaction-centric generator can subclass it instead of copying ~200 lines of walk.
h2. Scope of Work
* Create {{jstests/libs/util/change_stream/change_stream_fsm_command_generator.js}} — {{{}FsmCommandGenerator{}}}: {{{}constructor(seed){}}}/{{{}getSeed(){}}}, {{generateCommands(model, params)}} (BFS all-pairs shortest paths precompute, unvisited-edge iteration: random unvisited self-loo
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139314In Code Review
Use hangInStandbyReadLoop failpoint for disagg replication pause in multikey_timestamp_transaction_large_apply_ops.js
Replace {{pauseOplogApplication}} with {{hangInStandbyReadLoop}} in the disagg path of {{{}multikey_timestamp_transaction_large_apply_ops{}}}. This pauses receiving-side processing and lets oplog entries accumulate upstream, matching the test’s intended replication pause semantics.
PYTHON-6210In Progress
[Rust core] Audit PyMongo's platform and wheel matrix against Atlas driver metadata and Rust toolchain support
h3. *Context*
PyMongo ships binary wheels with a compiled C extension for a fixed platform matrix. A Rust-core PyMongo (PYTHON-6162) must ship on the same platforms.
Every PyMongo client sends an {{os}} document in the handshake {{client}} metadata; Atlas records it. Rust tiers 1 and 2 ship a prebuilt standard library; tier 3 does not (https://doc.rust-lang.org/rustc/platform-support.html).
Current wheel matrix ({{.github/workflows/dist.yml}}, {{[tool.cibuildwheel]}} in {{pyproject.toml
SERVER-137945Backlog
Store MCV and NDV in persistent stats
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-6211In Progress
[Rust core] Measure how many active clusters run PyMongo without the C extension
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
SERVER-139328Open
Increase sharded test coverage for create/collMod with persistentStatsConfig
Created from the following [comment|https://github.com/10gen/mongo/pull/66156#discussion_r4562593330]:
Add a test verifying that persistentStatsConfig are not lost when sharding a collection.
SERVER-139165In Code Review
Fix up exhausiveScope in a dotted path edge case
The exhaustiveScope of a deep path $set when a prior, shorter path exists (the shadowing case) is incorrect.
This is follow up from SERVER-131449, which grew in scope too much, so this bug fix was split up (see [vesko/SERVER-131449-Fix-up-exhausiveScope-in-the-shadowing-case]([https://github.com/10gen/mongo/pull/60571])).
The exhaustive scope selection should check for a missing parent embedded scope before falling back to the previous field's exhaustive scope. When the parent's embedded s
SERVER-138960Backlog
Add DSC multiversion test for binary upgrade, FCV upgrade/downgrade, and binary rollback on the same data
Upgrade: previous DSC release at fleet FCV X -> next release at FCV X -> {{setFCV Y}}. Rollback: {{setFCV X}} on the new release -> binary rollback to the previous release, on the same data.
No DSC test covers the last step: the previous release restarting on data that the new release wrote, including state written while the FCV was Y and still present after {{setFCV X}}. The new binary tolerates that state, so every existing suite passes. The old binary may fail to start or crash.
Existin
SERVER-138847Backlog
Add collMod support for creating foreign key constraints (unvalidated)
SERVER-138686Backlog
Remove _checkIndexBuildsInProgress step from ShardingCoordinator
The {{_checkIndexBuildsInProgress}} was introduced in order to avoid parallel running of index builds and DDL coordinators as a best-effort check.
With SPM-4906 this should be obsolete, so we should remove that code.
SERVER-138841Needs Scheduling
Evaluate wether to add readConcern logging for non-transactional external requests
In -[SERVER-44539|https://github.com/10gen/mongo/pull/66120]- we re-enable the missing RWC logging. As a follow-up, we should evaluate wether or not to add readCornern logging for non-transactional external requests without a readConcern or a custom cluster-wide default (referencing [this|https://github.com/10gen/mongo/pull/66120#discussion_r4478702587] PR comment). In this case, {{_extractReadConcern()}} early returns without reaching the check on the presence of a read concern, including on s