Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138368Backlog
Make ReshardingTest fixture handle concurrent resharding
Add a TestData flag (see configShard) that makes an additional resharding operation start in the background concurrently (_withOperationInBackground). It should be on a distinct namespace but on the same donors and recipient shards. it should complete before any consistency checks run. this should be feature flag gated for now, and not run in suites with older binaries. the background resharding should have its own state instead of reusing _ns, _tempNs, etc and shouldn't interfere with cluster-w
SERVER-138367Backlog
Add namespace to ReshardingTest fixture coordinator failpoints
ReshardingTest sets 3 failpoints: reshardingPauseCoordinatorBeforeBlockingWrites, reshardingPauseCoordinatorBeforeDecisionPersisted, and reshardingPauseCoordinatorBeforeCompletion. Only the last one filters by source namespace, the other two do not. if a second resharding coordinator ran on the same config server, the failpoints could cause them to hang. the approach should be to add executeIf and check for source namespace, and have the fixture passing the source namespace. might need to check
NODE-8007Investigating
node-mongodb-native - PR #5122: [Snyk] Upgrade @mongodb-js/saslprep from 1.5.0 to 1.6.1
[admin-token-bot|https://github.com/admin-token-bot] has created [PR #5122: [Snyk] Upgrade @mongodb-js/saslprep from 1.5.0 to 1.6.1|https://github.com/mongodb/node-mongodb-native/pull/5122] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
SERVER-138779In Code Review
Give NoLimitSorter two swapping buffers for incremental spilling
Incremental spilling needs a buffer that keeps receiving keys while another buffer's sorted keys are written out at the collection scan's rate. {{NoLimitSorter}} keeps one buffer and writes everything at once when it exceeds {{maxMemoryUsageBytes}}.
This gives {{NoLimitSorter}} two buffers that trade roles, each holding its unspilled entries and the pool its keys are allocated from; {{memPool()}} returns the filling buffer's pool, and memory accounting covers both. This is the structure only: n
NODE-8008Investigating
node-mongodb-native - PR #5123: [Snyk] Upgrade bson from 7.3.2 to 7.3.3
[admin-token-bot|https://github.com/admin-token-bot] has created [PR #5123: [Snyk] Upgrade bson from 7.3.2 to 7.3.3|https://github.com/mongodb/node-mongodb-native/pull/5123] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
SERVER-139110Open
Add zoned resharding coverage under continuous config server stepdowns
SERVER-138623 could have been caught if there were resharding with zones JS tests that induced stepdowns of config primary. No JS test combines resharding, zones, and a config primary failover as I looked.
{{sharding_csrs_continuous_config_stepdown.yml}} excludes all *reshard*.js with (TODO SERVER-51495),
{{concurrency_sharded_stepdown_terminate_kill_primary_with_balancer_and_config_transitions_and_add_remove_shard.yml}} and {{concurrency_resharding_with_lightweight_stepdowns.yml}} does st
NODE-7995Backlog
Driver fails to close the server monitors if part of MongoClient.close fails
h3. Use Case
As a... Node Driver user
I want... MongoClient.close to always close monitoring connections (even if close fails otherwise)
So that... monitoring connections are consistently closed and don't end up leaking
h3. User Experience
* `MongoClient.close` closes the monitoring connections, even if other parts of `close` fails
* users right now can workaround by calling MongoClient.close twice on the client
h3. Dependencies
* none
h3. Risks/Unknowns
* none
h3. Accep
Components
Server Selection
PYTHON-6273ClosedFixed
Let Dependabot fully manage uv.lock updates
h3. *Context*
Python dependencies are pinned by a single {{uv.lock}}, maintained by two writers: the weekly {{uv Lock Update}} workflow and Dependabot (security updates only). Dependabot resolves with the repository's {{exclude-newer}} setting, which corrupts its pull requests ([dependabot-core#14156|https://github.com/dependabot/dependabot-core/issues/14156]). S pull request can claim an update while removing or downgrading packages. and delays urgent security patches by up to a week. The e
Components
Infrastructure
Fixed Versions
4.20.1
SERVER-139436ClosedFixed
Honor bypassParallelGates knob in the parallelism planner size gate
Fixed Versions
9.1.0-rc09.1.0-rc1026
NODE-7342Backlog
Make `SelectServerOptions` internal
h3. Use Case
As a driver user,
I want select server options to be internal (it is not used in public APIs),
So that I can modify it as I please.
h3. User Experience
* _What is the desired/expected outcome for the user once this ticket is implemented?_
* _If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?_
h3. Dependencies
* We need to make sure this is deprecated first!
h3. Risks/Unknowns
* _N/A_
h3. Acceptance Criteri
Components
TypeScript
NODE-7914Investigating
Mandate raising writeConcernError (change SHOULD to MUST)
This ticket was split from {{{}DRIVERS-3684{}}}, please see that ticket for a detailed description.
h3. Expected Behavior
As a... _(who is this affects)_
I expect... _(describe behavior)_
When... _(trigger action)_
h3. Actual Behavior and Impact
* _What is the actual behavior?_
* _If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?_
h3. Dependencies
* _upstream and/or downstream requirements and timelines to bear in mind_
Components
CRUD & Command-Level Operations
NODE-8002ClosedDeclined
node-mongodb-native - PR #5115: docs: generate docs from latest main [skip-ci]
[github-actions[bot]|https://github.com/apps/github-actions] has created [PR #5115: docs: generate docs from latest main [skip-ci]|https://github.com/mongodb/node-mongodb-native/pull/5115] in [node-mongodb-native|https://github.com/mongodb/node-mongodb-native]
NODE-8004ClosedDeclined
js-bson - PR #963: chore(main): release 7.4.0
[github-actions[bot]|https://github.com/apps/github-actions] has created [PR #963: chore(main): release 7.4.0|https://github.com/mongodb/js-bson/pull/963] in [js-bson|https://github.com/mongodb/js-bson]
SERVER-134661Backlog
Support extensions on macOS
Extensions are currently only supported on linux platforms, since $vectorSearch/$search are only supported on those platforms.
We made some compromises during the implementation phase of extensions based on the assumption that we'll only support linux platforms. However, we may need to provide support for MacOS in the long term.
Investigate the work required to support extensions on MacOS on both x86 and arm.
todo items:
- GPG was brought into the build system in order to sign our tes
SERVER-134662In Progress
Provide support for extensions signature verification on Windows
The RNP library we use to perform signature verification of PGP signatures requires either openSSL or botan crypto backends. Windows platforms do not vendor in openssl. Historically, we avoided vendoring in openssl to prevent having to perform a mongodb upgrade to bump the openssl library when security vulnerabilities are detected in the library.
To support this, we’ll either need to vendor in openssl (undesirable), or use built in windows functionality for signature verification (i.e Authent
SERVER-138710In Progress
Set up CodeArtifact publishing, Evergreen CI, and end-to-end integration testing for mongo-extension-rust-sdk
h2. Description
h3. Background
The {{extension_sdk}} crate (Rust SDK for MongoDB server extensions) has no CI, no publishing pipeline, and no test coverage beyond unit tests. Consumers must install libclang to build it and depend on it via git tags rather than a registry.
h3. Work
* *Pre-generated committed bindings* ({{src/bindings.rs}}): drop the build script and bindgen dependency so consumers compile pure Rust with no libclang; regeneration documented in RELEASING.md
* *CodeArti
SERVER-137944ClosedFixed
Calculate MCV and NDV in one collection scan
Fixed Versions
9.1.0-rc0
NODE-7703ClosedDone
[waiting for server backport binaries] Unskip failing SDAM tests after server upgrade
[https://spruce.corp.mongodb.com/version/mongo_node_driver_next_16f6fb321ccfa2e1f21eb281befdae4e07ad736c/test-analysis?page=0&sorts=BASE_STATUS%3ADESC]
* SDAM_Unified_Tests_{_}Spec{_}_hello-timeout.Driver_extends_timeout_while_streaming
* SDAM_Unified_Tests_{_}Spec{_}_interruptInUse.Error_returned_from_connection_pool_clear_with_interruptInUseConnections_true_is_retryable
* SDAM_Unified_Tests_{_}Spec{_}_interruptInUse.Error_returned_from_connection_pool_clear_with_interruptInUseConnec
Components
SDAMSpec Test Coverage
Fixed Versions
7.9.1
SERVER-134365ClosedFixed
Create ExchangeGather stage
The stage has capabilities to start N thread and synchronize their work to produce the single output that the query plan expects from the stage.
Prepare those threads so that they have dedicate OperationContext, Client, etc... needed for correct execution of the subquery.
Wrap the thread execution in a try/catch to collect and report to the main thread any exception occurred during execution.
Rename the thread after the main thread name to ensure that log entries from the thread can be
Fixed Versions
9.1.0-rc09.1.0-rc1026