Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
CSHARP-6300Investigating
TLS handshake has no timeout: server monitor hangs forever since 3.5.0, pool connection opens hang without a cancellation token
**Driver:** 3.10.0 (same code in 3.5.0-3.13.0 and current `main`); also 2.24.0 for the pool part
**Runtime:** .NET 10 on Linux, `net6.0+` build of the driver, `tls=true`, replica set
**Server:** MongoDB 7.0 with `--tlsMode requireTLS`
### Summary
When a node accepts TCP connections but never answers (for example, its old connections are dropped silently without a RST), the TLS handshake of a new connection waits forever. This affects two code paths:
1. **Server monitor (regression in 3
SERVER-138538Needs Merge
Support collations in MCV Space Saving algorithm
Fixed Versions
9.1.0-rc09.1.0-rc1025
CSHARP-6301Ready for Work
Refactor/merge EndPointHelper and EndPointExtensions
Fixed Versions
4.0.0
CSHARP-6302Ready for Work
Remove settings references from events
Investigate and remove settings references from events, for example:
{{{}ConnectionPool{}}}-related events, some of them has property of {{ConnectionPoolSettings}} type, but not all:
With ConnectionPoolSettings:
- ConnectionPoolClearedEvent
- ConnectionPoolClearingEvent
- ConnectionPoolOpenedEvent
- ConnectionPoolOpeningEvent
- ConnectionPoolReadyEvent
Without:
- ConnectionPoolAddedConnectionEvent
- ConnectionPoolAddingConnectionEvent
- ConnectionPoolCheckedInC
Fixed Versions
4.0.0
CSHARP-6243ClosedFixed
Transactions unified test error-labels-blockConnection is flaky due to configuring its failpoint through a client with timeout options
This ticket was split from {{DRIVERS-3659}}, please see that ticket for a detailed description.
Components
Unified Test Format
Fixed Versions
4.0.0
SERVER-136465ClosedFixed
Triage tests in jstests/sharding that fail in disaggregated storage
SERVER-115493 included all of jstests/sharding in the no_passthrough_disagg_override_sharded suite. However, 100+ failing tests were put in an untriaged exclusion list.
This ticket should classify those failures by root cause, and open follow up tickets to fix those tests (or definitively exclude them if they test ASC exclusive functionality).
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137033ClosedFixed
Requests that arrive with trace info marked sampled are traced by default
Right now, commands with trace info are subject to sampling rates and rate limits. We should consider how to ensure that commands with trace info are always traced by default. Also add the ability to disable it as an emergency.
h2. Implemented on calvin.nguyen/otel-trace-perf (commit 9c616f6d1fe)
* An incoming trace is continued only if its \{{traceparent}} is marked sampled (\{{-01}}). Drivers propagate a \{{traceparent}} whether or not they are tracing, so continuing every incoming tra
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139011Needs Scheduling
Update Homebrew Formulae for New Major Patch Release (8.0.37)
Update Homebrew Formulae to support new Major Patch Version 8.0.37
SERVER-138911ClosedFixed
Remove dedicated test variant for replicated size and count
This variant is redundant after SERVER-117454.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139010Needs Scheduling
Update Homebrew Formulae for New Major Patch Release (8.3.16)
Update Homebrew Formulae to support new Major Patch Version 8.3.16
SERVER-100032Backlog
Add total spilling in explain output
SPM-3701 added four spilling metrics in all stages that spill
* spills // The number of times the stage has spilled
* spilledBytes // The amount in bytes of main memory that has been spilled
* spilledRecords // The number of records that have been spilled
* spilledDataStorageSize // The amount in bytes that spilling has taken up on disk
The stages report those metrics in their explain output but there is no accumulated result for the whole query. It would be nice to report the total of
PYTHON-6228ClosedDone
Enable ruff rules UP007 and UP045 to use `|` instead of Union and Optional
h3. *Context*
Ruff's https://docs.astral.sh/ruff/rules/non-pep604-annotation-union/ and https://docs.astral.sh/ruff/rules/non-pep604-annotation-optional/ rules replace {{Union}} and {{Optional}} in type hints with {{|}} to improve readability.
h3. *Definition of done*
Remove the suppression of UP007 and UP045.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
SERVER-139009Needs Scheduling
Update Homebrew Formulae for New Major Patch Release (6.0.30)
Update Homebrew Formulae to support new Major Patch Version 6.0.30
SERVER-138897ClosedFixed
Hash-pin GCP OIDC helper dependencies and clean up credentials on teardown failure
* *Hash-enforced installs*: {{evergreen/external_auth_gcp_requirements.txt}} gains sha256 {{--hash}} entries for every artifact of all 20 pins (generated with {{uv pip compile --generate-hashes --universal}}), and {{setup_gcp_venv}} installs with {{--require-hashes --only-binary=:all:}}, so index content outside the repo's committed wheels fails before it can run while GCP credentials are on disk. {{--only-binary}} is needed because {{--require-hashes}} does not cover the build dependencies pip
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-135520In Progress
Create test_utils for index and collection test setup
Create common facility for collection and index interaction. Replace repeated helpers with it.
SERVER-135523In Progress
Collect feedback: testing pain points from Server Engineering
Feedback doc: [https://docs.google.com/document/d/1VzIl-OWsdhFPChFUZ-ahmQQdlhABaXgUH39pGwwMAYE/edit?tab=t.0#heading=h.iicr4vl31nsd]
Key teams that are hit hardest by infinite burndown => have lots of test redness and rely on jstests: Sharding and Replication.
SERVER-138550Backlog
Classic $group ignores collation for BSON Symbol group keys
Classic $group (and the merging $group on mongos) ignores the collator when comparing and hashing BSON Symbol keys, so Symbols equal under the collation form separate groups.
* Repro, standalone with {{internalQueryFrameworkControl: "forceClassicEngine"}}: Symbols {{a}} and {{A}} grouped with collation {{{locale: "en", strength: 2}}} return two groups instead of one.
* Cause: {{Value::compare}} and {{Value::hash_combine}} do not apply the collator to Symbols.
* Found while fixing SERVER-137906.
SERVER-137872ClosedDuplicate
Analyze should persist max needed size of sample
Once SERVER-132398 and SERVER-137870 are complete, analyze should always persist one sample of the maximum size between CBR and JOO's requirements.
SERVER-138544Backlog
bulkWrite on sharded cluster ignores collectionUUID on write with repeated namespace
When a {{bulkWrite}} command sent through a 9.0 mongos has two or more {{nsInfo}} entries with the same {{ns}} but different {{collectionUUID}} values, mongos merges them into one entry and forwards it to the shard. Only the first entry's {{collectionUUID}} is kept, and it is checked for every op that targets that namespace. A first entry with no {{collectionUUID}} counts too: all later UUIDs for that namespace are then dropped.
As a result:
* A write with a stale {{collectionUUID}} can su
Components
ShardingWrite Ops
Affected Versions
8.3.139.0.4
SERVER-138870ClosedFixed
Delete unused legacy executor code
As of 671d414da30993624915a3ac7867c0754ce1d845, all of this code is unused. It was used in the legacy get executor which is being deleted and currently does not answer any queries
Fixed Versions
9.1.0-rc09.1.0-rc1025