Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138832Needs Scheduling
Complete TODO listed in SERVER-128219
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:57
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-128219&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 thi
SERVER-138687Needs Scheduling
movePrimary operation has overhead during index build check
{{_checkIndexBuildsInProgress}} was introduced as a best effort check to avoid running DDL operations during an active index build.
However the implementation on the movePrimary operation is not the most effective and has an overhead on untracked collections.
The implementation right now send out index build checks for each shard not taking advantage of the knowledge where the given namespaces exist.
This was an accepted overhead though knowing that SPM-4906 would render the whole checking
NODE-8005Backlog
[dbx-js-tools] update eslint to use flat config
h3. Use Case
As an eslint user,
I want to adopt eslint's flat config file format for my eslint configuration,
So that we can continue to update eslint once the legacy config format is removed in v10.
dbx-js-tools lints with ESLint v9 through {{.eslintrc.json}} and the {{ESLINT_USE_FLAT_CONFIG=false}} environment variable. ESLint v10 removed support for the legacy config format, so {{npm run check:eslint}} fails on v10 with "ESLint couldn't find an eslint.config.* file".
See
* https://typescri
NODE-8006Backlog
[dbx-js-tools] upgrade eslint v9 -> v10
h3. Use Case
As a mongodb node driver developer
I want to use the latest major version of eslint (v10) in dbx-js-tools
So that compatible plugins and dependent packages can be updated, promoting maintainability
h3. User Experience
* eslint checks should pass with the same rule parity following the v9 non-flat configuration file
h3. Dependencies
* The flat config migration for dbx-js-tools (the "[dbx-js-tools] update eslint to use flat config" sibling subtask), because eslint v10 only reads {{
SERVER-139177ClosedFixed
Emit ceSamplingMetadata and fieldStatsMetadata namespaces in sorted order in explain
{{queryPlanner.ceSamplingMetadata}} and {{queryPlanner.fieldStatsMetadata}} are stored in {{{}StringMaps{}}}, so explain lists their namespaces in hash-map order. That order can change between runs, so any golden tests would have to sort these themselves for a deterministic order.
Useful for SERVER-139074.
Fixed Versions
9.1.0-rc09.1.0-rc1026
NODE-7993Blocked
JS MongoDB checkpointer: store each LangGraph state channel separately
h4. TL;DR
{{MongoDBSaver}} in {{langgraph-checkpoint-mongodb}} saves the entire agent state as one MongoDB document on every step. Once the combined state passes MongoDB’s 16 MB document limit, the run fails. Store each large state channel as its own document and write only the channels that changed.
h4. Context
LangGraph is a framework for building AI agents as graphs. A _checkpointer_ saves the agent’s progress after each step, so a run can resume after a crash, pause for human input, o
Components
ABX
SERVER-123168Open
[Join Optimization] Code cleanup: Don't pass SamplingEstimators to JoinCardinalityEstimator
After SERVER-122916, JoinReorderingContext has a reference to SamplingEstimatorMap. This means we can remove the SamplingEstimatorMap parameters to JoinCardinalityEstimator functions ([example|https://github.com/10gen/mongo/blob/ffa2a9d8559f4bdbd673f0eed04b046951a40b0d/src/mongo/db/query/compiler/optimizer/join/cardinality_estimator.h#L55]).
SERVER-139241ClosedDone
express_write_id_with_embedded_eq.js fails in multi_stmt_txn passthroughs
The upsert case added by SERVER-138035 expects {{DollarPrefixedFieldName}}. In the multi_stmt_txn passthroughs, that error aborts the wrapping transaction, which also rolls back the {{beforeEach}} insert. The shared {{afterEach}} then finds an empty collection: {{expected [ ] to equal [ [Object], [Object] ]}}.
*Fix:* Move the upsert case into its own {{describe}} block, starting from an empty collection that is committed before the upsert runs. The other cases keep their transaction coverage.
NODE-7907ClosedDone
Update dependencies for kerberos
h3. AC
* Merge dependabot PRs that are safe to merge (semver-compatible updates, including any standalone package-lock-only PRs)
* When updating the dev dependencies to latest available semver compatible versions ANY reformatting MUST be done in a separate pull request and should ONLY be done if the team agrees that it is an important improvement
* Check dev dependency major version updates
** Update the major version if and ONLY if this can be done with minimal code changes; otherwise, file
Fixed Versions
kerberos-7.1.0
SERVER-69257ClosedFixed
COUNT_SCAN plan not selected when unfiltered $group + $sum on _id performed
As of DRIVERS-501 the driver [CRUD specification|https://github.com/mongodb/specifications/blob/master/source/crud/crud.rst#countdocuments] defines a pipeline to be used to count documents without resorting to the [{{count}} command|https://www.mongodb.com/docs/manual/reference/command/count/] (due to potential [inaccurate counts without query predicates|https://www.mongodb.com/docs/manual/reference/command/count/#inaccurate-counts-without-query-predicate]).
Without specifying a {{filter}}
Components
Query Planning
Fixed Versions
9.1.0-rc09.1.0-rc1024
SERVER-139257Backlog
Extract concurrency limited queue into its own class
Create a class that abstracts the concurrency limited queue behavior present in the range deleter in order to decouple the task scheduling logic from the range deleter.
The class would follow a layout similar to this:
SERVER-86194ClosedFixed
Improve MatchExpression $or->$in rewrite to handle multiple fields
Currently the MatchExpression $or->$in rewrite is only capable of collapsing a single field with multiple equality disjunctions into a $in. For example,
is optimized to
This leads to an SBE plan with a large number of unnecessary comparisons. SBE is able to evaluate $in predicates more efficiently by using a hashset, and the interval builder is able to generate index bounds more easily on an $in list.
These expressions can be further reduce by allowing the $or->$in r
Fixed Versions
8.0.0-rc0
SERVER-139315Needs Scheduling
Record types of computed fields
We currently do not type computed fields like:
{$set: \{a: {$add: [...]}}
{$set: \{a: {$toLower: "$b"}} etc.
Suggested solution
The general practice in the dependency graph has been to compute the metadata of fields when we process the stage declaring the field, and to do additional type narrowing, using applicable $match stages, between the declaration site and the call site.
I think we can continue that pattern. We already process per-expression dependencies at [processExpressio
NODE-7900In Progress
Update project dependencies
h3. Use Case
As a... Node driver engineer
I want... to have up to date dependencies
So that... we can be more efficient by using the best available tools
h3. User Impact
* N/A
h3. Dependencies
* N/A
h3. Unknowns
* Do we want to update any previous majors?
h3. Acceptance Criteria
h3. Implementation Requirements
* Review and update the dev and prod dependencies in the following libraries:
** driver
** js-bson
** mongo-client-encryption
** kerberos
** zstd
** dbx-js-tools
** mongodb-
Components
Dependencies
SERVER-139295ClosedFixed
Retry WriteConflict when acquiring/promoting/releasing the critical section
*Issue*
During a DSC step down, DDLs can bubble up a WriteConflict error to the user (instead of the critical section code internally retrying it).
*Analysis*
[Acquiring, promoting or releasing the critical section writes via DBDirectClient with locks held|https://github.com/mongodb/mongo/blob/b2b94807a4d84159532979b97387cc806f691e0e/src/mongo/db/global_catalog/ddl/sharding_recovery_service.cpp#L282-L364].
In a DSC cluster, during stepdown we may hit a WriteConflict there due to
Affected Versions
9.1.0-rc0
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-137182In Progress
Parent task tracking work for exposing query knobs for PQS
See the syntax doc for the list of knobs. This should involve:
* updating each existing knob to be visible via query settings
* updating sites where we check the knob to use the QKC context/ not use the knob directly
* adding tests validating each knob does the right thing for all its values
* adding tests to verify interactions between related knobs work as expected
SERVER-139082ClosedFixed
Enable multikey_timestamp_mixed_transaction_large_oplog_batches.js in no_passthrough_disagg_override_replsets
The test pauses secondary replication using {{stopReplProducer}} before executing its mixed workload. DSC bypasses the conventional oplog fetcher that checks this failpoint, so the test waits 10 minutes and fails with {{MaxTimeMSExpired}} before exercising its multikey timestamp assertions.
As part of this ticket, we have to adapt this test by using {{pauseOplogApplication}} on the secondary when running under DSC. We have then enable the test in {{no_passthrough_disagg_override_replsets.}}
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139312In Code Review
Enable check_metadata_consistency_collmod_frozen_chunk_operations.js in no_passthrough_disagg_override_replsets
The test pauses {{collMod}} after the global catalog update but before shard-local updates, catches up the secondaries, then stops replication on one secondary. It resumes {{collMod}} and verifies that metadata consistency checking at the lagged secondary’s timestamp does not report a spurious {{{}CollectionOptionsMismatch{}}}. Finally, it restarts replication and checks consistency again. Under DSC, {{stopServerReplication()}} invokes a fixture-wide override that stalls primary log progress rat
SERVER-139260In Code Review
Enable direct_shard_connection_auth_rs_commands.js in no_passthrough_disagg_override_replsets
The {{allows replSetStepDown and replSetStepUp}} case in {{direct_shard_connection_auth_rs_commands.js}} assumes that promoting a secondary leaves the former primary running and able to become secondary. In DSC, unconditional step-down shuts down the former primary rather than transitioning it in-process (tracked by SERVER-124385). Consequently, the test's subsequent topology waits and cleanup cannot assume all members remain available. In addition, {{replSetMaintenance}} and {{replSetAbortPrima