Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
GODRIVER-4115Backlog
Benchmark OpenTelemetry support
This ticket was split from {{DRIVERS-3620}}, please see that ticket for a detailed description.
Components
Observability
GODRIVER-3462ReleasedDone
Improve Error Messaging
{panel:bgColor=#fafbfc}
We can significantly improve error messaging and debug-ability by adding context to errors as we return them (i.e. by wrapping errors). We can also "join" errors that occur during operation retries, allowing us to see the full history of an operation in a single error, including all retries. Those together should make it way easier to debug some Go Driver errors.
{panel}
SERVER-137330In Code Review
Propagate SBOM team ownership to dependencies and record team_responsible provenance
h2. Overview
Vulnerability tickets for third\-party dependencies are routed by {{internal:team\_responsible}} on the component in Dependency\-Track. Only components with an explicit owner have it, so vulnerabilities in their direct and transitive dependencies \(for example the 219 dependencies of {{pkg:maven/com.mongodb.streams/aspio}}, owned by Atlas Stream Processing Engine\) fall back to Server Triage.
h2. Scope of Work
\* {{buildscripts/sbom/sbom\_utils.py}}: add {{propagate\_team\_ownershi
PYTHON-6230ClosedDone
Enable ruff rule UP041 to unify TimeoutErrors
h3. *Context*
Since Python 3.11, TimeoutError and asyncio.TimeoutError are identical. Ruff's UP041 rule (https://docs.astral.sh/ruff/rules/timeout-error-alias/) enforces the use of {{TimeoutError}} automatically.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Remove the suppression of UP041.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
SERVER-138476In Progress
Fix initial sync log ingestion rule
A recently added log ingestion rule on log ID 21237 captures some log entries that it should ignore. For example, we purposely fail an initial sync if it would copy the FCV document since that is not supported, so we should not trigger the log ingestion rule on cases like this
JAVA-6343ClosedDuplicate
Update libmongocrypt to 1.21.1
Update [mongodb-crypt|https://mvnrepository.com/artifact/org.mongodb/mongodb-crypt] to bundle libmongocrypt 1.21.1.
GODRIVER-4238ClosedDone
mongo-go-driver - PR #2703: Bump anthropics/claude-code-action from 1.0.262 to 1.0.266 in the actions group
[dependabot[bot]|https://github.com/apps/dependabot] has created [PR #2703: Bump anthropics/claude-code-action from 1.0.262 to 1.0.266 in the actions group|https://github.com/mongodb/mongo-go-driver/pull/2703] in [mongo-go-driver|https://github.com/mongodb/mongo-go-driver]
GODRIVER-4240ClosedDone
mongo-go-driver - PR #2705: Merge release/2.9 into master
[mongodb-drivers-pr-bot[bot]|https://github.com/apps/mongodb-drivers-pr-bot] has created [PR #2705: Merge release/2.9 into master|https://github.com/mongodb/mongo-go-driver/pull/2705] in [mongo-go-driver|https://github.com/mongodb/mongo-go-driver]
SERVER-134902Open
Increase replWriterThreadCount during initial sync
Since we are able to change replWriterThreadCount at runtime now, we should leverage this to try and get better initial sync performance. Past experiments have shown that initial sync benefits a lot from increase the replWriterThreadCount parameter, so we should dynamically change this parameter during initial sync to try and get the best performance out of the system that we can.
This will also need to include a way to toggle this functionality off
SERVER-137924In Progress
Model changes making initial sync catch up to current cluster view in TLA+
We want to make changes so that initial sync (LIS or FCBIS) is not considered completed until it is caught up to the primary’s view of {{max(lastCommitted, my lastWritten)}} (from the beginning of initial sync). This should be modeled TLA+.
SERVER-138680Backlog
Ensure spilling hash agg yields resources
This is the task to cover spilling hash agg induced resource contention. Description in linked ticket.
SERVER-138483ClosedWon't Do
Treat constant $group keys as eligible for streaming group
A {{$group}} with a constant key such as {{_id: null}} is not eligible for streaming group. All documents form one group, so streaming applies trivially.
* Found in review of the PR for SERVER-136171.
* Update the eligibility counter test and planner unit tests that expect ineligibility.
SERVER-137029Investigating
Minimize the cost of trace sampling decisions
h2. Goal
Make the decision "should this request be traced?" cheap: free when nothing can be sampled, and near-free at the default sampling rate, where nearly every request is still rejected. The scope doc's target is under 2% CPU at the default level.
h2. Changes
h3. 1. Fast sampling roll (land first)
Every sampleable root span draws a roll with \{{PseudoRandom::nextCanonicalDouble()}}, i.e. libstdc++'s \{{std::generate_canonical}}, which computes in \{{long double}} with two \{{logl}} c
CSHARP-5570Investigating
Add test for SRV hostname validation when resolver and resolved hostnames are identical with three domain levels
This ticket was split from {{DRIVERS-3162}}, please see that ticket for a detailed description.
Components
Initial DNS Seedlist Discovery
CSHARP-6218Backlog
Benchmark OpenTelemetry support
This ticket was split from {{DRIVERS-3620}}, please see that ticket for a detailed description.
Components
Observability
CSHARP-6294Ready for Work
Investigate how to publish nuget packages with Trusted Publishing approach