Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139071ClosedGone away
Collection metadata recoverer incorrectly marks untracked collections on the config database as "unowned"
The DB primary of the config database is the config server. When recovering authoritative metadata, the config server should mark each untracked collection in the config database as "untracked", but instead it [marks it as unowned|https://github.com/10gen/mongo/blob/d66cb87b8981b27cfa97c374d02c24cb2f5ac4b6/src/mongo/db/shard_role/shard_catalog/collection_metadata_recoverer.cpp#L358-L376]. This doesn't have much consequence beyond [making CMC complain about it|https://github.com/10gen/mongo/blob/
SERVER-119957Open
Investigate whether SBE plans generated by the join optimizer yield frequently enough
The join optimizer produces new kinds of SBE plans which may have different data access patterns than plans generated in the past. We should investigate whether the SBE engine's yielding behavior is sufficient, or whether it is possible for the join optimizer to generate a plan that (depending on the shape of the data) may not yield for seconds or minutes. My recollection is that SBE plans currently trigger yielding at the leave stages doing data access ({{scan}} or {{ixscan}}), but perhaps it i
SERVER-133099ClosedFixed
Add server parameter and allow to drop system.session for a sharded cluster
Add a new undocumented parameter to enable the drop of `system.session` collection on a sharded cluster.
The parameter is only meant to be used by specialized operators by following a documented playbook.
To serialize with potential concurrent creations (the collection is forced re-created every 5m) we guarantee to re-use the same shard as coordinator (i.e the first shard alphabetically).
Considering `addShard` or `removeShard` could potentially change the first shard alphabetically, the play
Components
Upgrade/Downgrade
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139284ClosedFixed
Consider which team should own the core_analysis tasks, and have the generator tag them
Core analysis generator is owned by test infra. It is one of the things flagged by the new Evergreen project setting for dynamic task owner tracking, as generating tasks without owner, once the bulk of the dynamic tasks generated by version_gen were handled.
Debate is whether it should be owned by the team who owned the task that _caused_ it to be generated, or always by test infra. Sounds like the latter.
Components
Testing Infrastructure
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138854Backlog
Investigate duplicate join plan cache entries from settings that don't affect plans
The join plan cache key now includes query settings: SERVER-137120, which follows the same approach as the classic planner. Queries with the same shape but different settings that don't affect the plan selection (comment, maxTimeMS) get different cache entries, since the hash function and equality check on JoinPlanCacheKey are not aligned. These entries hold equivalent plans, so we store duplicates and may replan equivalent queries.
Empty and unset queryKnobs may also produce equivalent plan
SERVER-139017ClosedDone
Arbitrary schema lead to 20% FTDC size increment
https://jira.mongodb.org/browse/BF-46667 reported that with https://jira.mongodb.org/browse/SERVER-130148 and new driver now send backpressure flag, size of compressed FTDC file increased by 20%. According to multipatch experiments, this is mainly because of the schema changes for FTDC compressor.
Fixed Versions
9.1.0-rc09.1.0-rc1026
NODE-8014Needs Triage
Change npm prepare script to prepublishOnly
h3. Use Case
As a... mongodb driver user
I want... to not be prompted to allow the driver's prepare script
So that... I can have one less item in the list of allowed scripts
h3. User Experience
This prints when installing the driver:
The driver's prepare script is not meant for the released version, it compiles the TS if tsc if available. It shouldn't be recompiling upon install and its not necessary to run in order to use the package.
h3. Dependencies
* None
h3. Risks/U
SERVER-139201ClosedFixed
Disallow `sampleSize` parameter to `analyze` command in sample mode
When writing samples, we no longer take the sample size as a parameter to the `analyze` command. However, `sampleSize` remains a parameter because histograms mode uses it.
To avoid confusion, we want to add a `uassert` that blocks users from calling `analyze` in sample mode and passing the `sampleSize` parameter.
Fixed Versions
9.1.0-rc09.1.0-rc1026
NODE-7888Backlog
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
NODE-7992Backlog
Add prose tests that a top-level error halts client bulkWrite execution (ordered and unordered)
This ticket was split from {{DRIVERS-3699}}, please see that ticket for a detailed description.
Components
CRUD & Command-Level Operations
NODE-7989Backlog
[Mastra] Update tests in AI/ML Pipeline
h2. TL;DR
The Mastra job in the AI/ML testing pipeline skips every test that needs Automated Embedding or a live Atlas cluster. Turn those tests on, and add a weekly run against.
h2. Context
[ai-ml-pipeline-testing|https://github.com/mongodb-labs/ai-ml-pipeline-testing] runs each AI framework's MongoDB tests every day against current MongoDB versions. For Mastra, the [{{test-mastra-js-local}}|https://github.com/mongodb-labs/ai-ml-pipeline-testing/blob/main/.evergreen/config.yml] task run
Components
ABX
NODE-7997Backlog
[AWS Strands] Add TypeScript implementation
Implement typescript implementation within the monorepo, creating with a 'typescript/' directory sibling to existing 'python/' one. Also create 'ci-typescript.yml' and 'release-typescript.yml'
h3. \/\/\/ What follows to be filled out. \/\/\/
h3. Use Case
As a... _(who is this for)_
I want... _(what is the desired change)_
So that... _(why is the change desired)_
h3. User Experience
* _What is the desired/expected outcome for the user once this ticket is implemented?_
* _If bug: W
NODE-7437Investigating
EJSON.stringify() replacer array should add data types
h3. Use Case
As a developer
I want to add a replacer array to EJSON.stringify without adding $oid, etc
So that I can get a stringified EJSON without worrying about the data types being removed
h3. User Experience
h3. Dependencies
None
h3. Risks/Unknowns
* _What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)_
It modifies the current behaviour of a replacer array. Therefore
Components
EJSONExtended JSON
Affected Versions
7.2.0
SERVER-135340Open
Ensure $persistedStats works for NDV stats too
The $persistedStats stage should also be able to read the contents of the system.stats.field_stats collection (which has NDV information), not just the system.stats.samples collection. Related to SERVER-124331.
NODE-7627Backlog
Remove ObjectId.cacheHexString
In the next major version of bson, remove the deprecated {{ObjectId.cacheHexString}} flag along with its supporting hex-string cache: the module-level {{__idCache}} WeakMap, the cache reads and writes in the constructor / {{toHexString()}} / the {{id}} setter, and the {{isCached()}} helper.
Depends on NODE-7626 (deprecation) shipping in a 7.x minor first.
Precedent: the equivalent flag on the UUID class was removed in NODE-5223 ({{feat(NODE-5223)!: remove deprecated cacheHexString}}). Once thi
Components
BSON
NODE-8001Investigating
node-mongodb-native - PR #5114: ci(deps-dev): bump the development-dependencies group across 1 directory with 10 updates
[dependabot[bot]|https://github.com/apps/dependabot] has created [PR #5114: ci(deps-dev): bump the development-dependencies group across 1 directory with 10 updates|https://github.com/mongodb/node-mongodb-native/pull/5114] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
SERVER-139331In Code Review
Re-enable lagged_config_secondary.js in no_passthrough_disagg_override_sharded
{{The lagged_config_secondary.js}} test verifies that mongos times out when the only reachable config-server secondary is behind the required metadata timestamp. The test currently uses {{stopServerReplication()}} to lag one secondary. Under DSC, this helper stalls primary-side replication across the replica set instead of pausing only the selected standby, so it does not preserve the intended scenario.
As part of this ticket, we should 1) Adapt the test for DSC, and 2) Add the test to {{no_p
Fixed Versions
9.1.0-rc09.1.0-rc1026
NODE-3ClosedDone
Db() logger option is not documented
Server() supports a logger method, which is documented here: http://mongodb.github.com/node-mongodb-native/api-generated/server.html
According to the [0.9.6-20 2011-10-04 changelog entry|http://mongodb.github.com/node-mongodb-native/changelog/changelog.html?highlight=logger#id46], Db() also supports this option, but it isn't documented here: http://mongodb.github.com/node-mongodb-native/api-generated/db.html
SERVER-138369Backlog
Add concurrent_resharding matrix suites for ReshardingTest suites
add an override under buildscripts/resmokeconfig/matrix_suites/overrides that sets the fixture flag from SERVER-138368, plus one mapping for each of: sharding, sharding_auth, sharding_config_shard, sharding_clustered_collections, and no_passthrough. add the evergreen task definitions so the suites run in CI. if any server bugs pop up while testing on evergreen, create separate tickets for those fixes.