Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
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
SERVER-139080Backlog
Investigate the monguard FindFilterSort tail regression
SERVER-137897 found one workload shape (FindFilterSort in top_ten_queries_locust) where monguard costs more than noise with socket handoff. It measured these latencies:
||Arm||p95||p50||avg||
|No monguard|3.01ms|1.81ms|2.33ms|
|Monguard proxy|5.91ms|2.71ms|3.70ms|
|Monguard handoff|4.89ms|2.24ms|3.08ms|
Handoff recovers part of the proxy regression. Handoff p95 latency is 1.9ms (~60%) higher than no-monguard (n=1). The original SERVER-137897 report calculated the regression as +37% p95
SERVER-138125ClosedDuplicate
Membership-based rid honoring in oplog application
The applier honors {{rids}} iff the node holds a {{groupId}}, replacing the per-collection catalog check. This is the core of the feature: in-group nodes apply updates and deletes by {{rid}}, out-of-group nodes fall back to {{_id}} lookup.
h2. Details
- Relax [tassert 11454701|https://github.com/10gen/mongo/blob/5fce3b99dea39b4f9453477819cedd935fba9a2c/src/mongo/db/repl/oplog.cpp#L2590] ({{rid}} presence iff collection option) to a membership-plus-in-scope check.
- In-group: inserts at the
SERVER-124059ClosedFixed
fix bazel wrapper nested python installs
some of our wrapper target run nested multiple bazel commands, causing the intermittent issues in the way python is detecting the current modules in the python path.
common failure mode would be something like:
Traceback (most recent call last):
File "/data/OTHER_HOST/mongo/bazel/wrapper_hook/wrapper_hook.py", line 193, in <module>
main()
File "/data/OTHER_HOST/mongo/bazel/wrapper_hook/wrapper_hook.py", line 86, in main
from bazel.auto_header.auto_header import gen_auto_hea
Fixed Versions
9.0.0-rc08.3.18
SERVER-127745ClosedFixed
Resharding recipient service deadlock on rapid stepdown then stepup
A resharding recipient node can permanently deadlock during step-up: it wins the election and reports PRIMARY, but never becomes a writable primary. The node logs 8025900 ("onStepUpComplete stepping up all services") but never 21331 ("Transition to primary complete"), and stays in this state until the process is killed. Reproduced on v8.0 and master; observed in production in HELP-93835 (v8.0.19).
h3. How the deadlock forms
It takes two failovers of the same node while the resharding recipie
Components
Index Builds
Fixed Versions
9.1.0-rc09.0.48.0.378.3.18
SERVER-132822ClosedFixed
createIndexes reports success without creating the index when a concurrent moveCollection replaces the collection
{{createIndexes}} can reply {{ok: 1}} without having created the requested index. The client is
told the index exists, and any later operation on it fails with {{IndexNotFound}} for example.
h2. How it happens
# {{createIndexes}} resolves the target collection UUID and releases all locks, then blocks in the
{{maxNumActiveUserIndexBuilds}} queue in {{IndexBuildsCoordinatorMongod::_startIndexBuild()}}. The
config fuzzer had set the knob to 1, so the wait lasted ~15 seconds.
# A concurrent
Fixed Versions
9.1.0-rc09.1.0-rc10229.0.9
SERVER-135202ClosedFixed
Make gRPC concurrent connection unit tests use a larger timeout
Please refer to [this comment|https://jira.mongodb.org/browse/BF-46196?focusedCommentId=8915212&focusedId=8915212&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-8915212] in BF-46196 for context.
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.78.3.18
SERVER-135720ClosedFixed
Disable mongor tests
These tests are generating BFs but are testing a feature which is no longer under development or supported.
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.78.3.18
SERVER-136131ClosedFixed
Fail fast DDL operations if there is an index build running on affected namespaces
Right now the DDL operations does not respect running index builds.
This can lead to availability issues like in HELP-97655 and HELP-97212.
Some custom error handling is already applied to handle this edge case in some DDL coordinator (like SERVER-117624), but there is no generic solution implemented yet.
This task is about adding a generic best effort check for DDL operations to avoid running during an active index build on the affected namespaces.
* The solution should be a best effort che
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.9
SERVER-135803ClosedFixed
Fix UnorderedTicketSemaphore timing out after a permit becomes available
{{UnorderedTicketSemaphore::acquire}} ignored the boolean result from {{{}_permits.waitUntil{}}}. With a short explicit deadline, a waiter awakened by a newly released permit could be mistaken for a deadline expiration because {{{}deadline == until{}}}. This could return a false timeout even though a ticket was available
As part of this ticket we should check the {{waitUntil}} result and enter the timeout path only when {{!waitResult && deadline == until.}}
Affected Versions
8.3.0-rc09.0.0-rc09.1.0-rc0
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.78.3.18
SERVER-136697ClosedFixed
Retry change stream FSM DDL commands on concurrent index builds
The change stream sharding FSM tests run two writers against the same database (`test_cs`) with different collections. The writers run independent command streams, so one writer can start an index build (`createIndexes` / `shardCollection`) on its collection while the other issues a database-level DDL command. In particular, a `movePrimary` on test_cs races with a sibling writer's index build: the `movePrimary` coordinator scans the database for in-progress index builds and rejects the command w
Components
Change streamsTesting Infrastructure
Fixed Versions
9.1.0-rc09.1.0-rc10249.0.9