Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
PYTHON-6205ClosedDone
Reduce flakiness of DNS tests
h3. *Name of Failure:*
test.asynchronous.test_dns.TestDNSSharded.test_srvMaxHosts-equal_to_srv_records
h3. *Link to task:*
https://spruce.corp.mongodb.com/task/mongo_python_driver_test_macos_arm64_test_standard_v9.0_python3.14_async_auth_ssl_sharded_cluster_3a8088d1b528fec6ac228c4ff4a774ddd6fd62bc_26_10_29_17_31_15/tests?execution=0&sorts=STATUS%3AASC
h3. *Context of when and why the failure occurred:*
A heartbeat to one mongos fails and waits the full 10 seconds to retry, which causes
SERVER-136246ClosedWon't Fix
Investigate TSBlock::getMin/Max and see if we can apply this to either ColumnarSample or Column
SERVER-137544ClosedFixed
Mark STAGE_SKIP as not parallel supported
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137671ClosedFixed
Handle signed integer overflow in simple8b prefixSum overflow
Fixed Versions
9.1.0-rc1025
GODRIVER-4202Ready for Work
Add vanity import path tests for go.mongodb.org CloudFront/S3 origin migration
h3. *Context*
Verify go.mongodb.org resolves the Go driver correctly after its migration to a CloudFront + S3 origin (DEVPROD-42795). The tests here are likely sufficient: https://github.com/10gen/go-driver-tools/blob/main/preston/repros/go.mongodb.org/devprod_42795_test.go they run against the 1.18, 1.21, 1.23, 1.25, and 1.26 runtimes over all driver versions. There are two tests:
* TestVanityImportMatrix: Runs go get and go build for every driver version on each Go runtime, resolving dir
PYTHON-6056ClosedDone
Search index helper prose tests are flaky
All of the search index helper prose tests are consistently flaky due to search index management issues.
Components
greenerbuild
SERVER-137589ClosedFixed
Make SBE $sum/$avg state available outside VM
This change makes double double summation state available outside of the VM. The state is stored on a struct. The struct provides read/write methods to transform to/from the SBE array state representation. This dedups some logic between $sum and $avg.
This also unlocks future work that uses the struct directly without the SBE array.
Fixed Versions
9.1.0-rc09.1.0-rc1025
JAVA-6263Investigating
Add Atlas integration tests for vector search against nested embeddings and arrays of embeddings.
Add integration tests for vector search against nested embeddings and arrays of embeddings.
See: https://github.com/mongodb/mongo-java-driver/pull/2026#issuecomment-5103116489
Components
Atlas TestingTest Coverage
SERVER-137943ClosedFixed
Switch to using SBE values in NDV computaions
The similar was it is done for MCV by Milena
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-135757ClosedFixed
Prevent delinquency in $update with set of a deep-array index
Setting a deep array index (for example, $set: \{“a.1500001”: 1}) forces path_support.cpp::maybePadTo to append up to 1.5 million null BSON elements to the array one at a time in a loop without interrupt checks. We can easily remediate this by adding a periodic check inside maybePadTo().
Add periodic check in maybePadTo(). There is already a stage in the [delinquency workload |https://github.com/10gen/dsi/pull/6140/changes#diff-d6d429934912251b7f1c6fffea50a52a2369714f64232bb284c691ee8100
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-134314ClosedFixed
LocalReshardingOperationsRegistry mutations in ReshardingOpObserver aren't tied to WriteUnitOfWork commit
{{ReshardingOpObserver}} calls {{{}LocalReshardingOperationsRegistry::registerOperation(){}}}/{{{}unregisterOperation(){}}}/{{{}clearOperationsForRole(){}}} directly, inline, from its {{{}onInserts{}}}/{{{}onUpdate{}}}/{{{}onDelete{}}}/{{{}onDropCollection{}}} hooks. These hooks run _before_ the enclosing {{WriteUnitOfWork}} commits, but the registry mutation itself is a plain in-memory update with no ties to whether that {{WriteUnitOfWork}} actually commits or rolls back.
So the registry's v
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136633ClosedFixed
Add JS test for per-collection size and count CRUD in steady state
After SERVER-136557 and SERVER-136623, we can implement a JS test for checkpoint validation in steady-state. Manually enable the server parameter and check that the checkpointsValidated metric is incremented. Then, induce a validation failure somehow, and check the node crashes.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138111ClosedFixed
[POA] Enable POA build variant
[It isn't turned on at the moment.|https://github.com/10gen/mongo/blob/53ac306590b5fc3ab265b6dc46293202d582fdb7/etc/evergreen_yml_components/variants/amazon/test_dev_master_branch_only.yml#L460]
Fixed Versions
9.1.0-rc0
SERVER-137217ClosedFixed
Include the BSONColumn decompressor's reason in validate results
SERVER-128900 replaced every BSONColumn decompression failure in validate results with the fixed description {{{}BSONColumn decompression failed{}}}, because the decompressor's own messages were assumed to contain document data. However, this means that there are some issues that can be over-indexed on right now. We should make it so that we do include the reason that we fail, so we can narrow down in the attribution what is the issue.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138196In Code Review
Dont add debug_names to rust debug info
Currently the core analyzer fails if you already have a debug_names section in your debug info. This makes it so llvm doesn't add these sections to rust code. GDB doesn't use this section and is the debugger we end up using.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-135754ClosedFixed
Update $sort’s custom comparator to check for interrupt every few thousand documents.
Tune the gap between interrupts to be approximately 5ms. Run extensive performance testing to ensure minimal regressions occur.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137555ClosedFixed
Add opt-in Windows persistent-container action runner
Windows cross links can exceed RBE's output limits when producing large PDBs. Add `windows_container_action_wrapper.py` so opted-in Windows cross builds run `CppLink` in a persistent local Linux container using the pinned RBE image, while compilation continues remotely.
Reuse the merged `container_action`, `container_engine`, `container_paths`, and config-publication helpers for detached output transport, engine recovery, mount validation, and locking. `cross/windows.py` selects the Linux eng
Fixed Versions
9.1.0-rc09.1.0-rc1025
CSHARP-5857Blocked
Support MongoDB OIDC Built-in Authentication for access to MongoDB with AWS Principals
This ticket was split from {{DRIVERS-3372}}, please see that ticket for a detailed description.
Components
Authentication
CSHARP-4721Blocked
Indicate the last operation in a transaction in a $changeStream event
This ticket was split from {{DRIVERS-2660}}, please see that ticket for a detailed description.
SERVER-134758ClosedFixed
validate command does not fail if schema non-compliant documents exist at validationLevel constraint
Since validationLevel constraint requires all documents to be compliant for optimizations to work, the existence of non-compliant documents on a primary should be treated as data corruption. the validate command should fail and trigger an AF.
The optimizer and execution plans for queries will eventually rely on these schema constraints and could crash a node if they are not held, so it is better to catch it earlier when running the validate command periodically.
The remediation would be to
Fixed Versions
9.1.0-rc09.1.0-rc1025