Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
GODRIVER-2123Backlog
Use an administrative Client in test runners
Both unified test runners currently use a single client for administrative actions (creating initial colllections, tearing down failpoints, etc.) and actual test operations. Ideally, these administrative actions would be done through a separate client that was unaffected by client options set in the test file (such as {{socketTimeoutMS}} or {{serverSelectionTimeoutMS}}). At the moment, we have to skip two SDAM tests that setup a failpoint and use a socket or server selection timeout since the fa
Components
Testing
SERVER-135194ClosedFixed
Add benchmark and jstest for query stats $match pushdown
Fixed Versions
9.1.0-rc09.1.0-rc1026
PYTHON-6284Needs Triage
Investigate automated greener build rotation slack handle + github reviewer assignment
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
{color:#505f79}other teams on slack have @<team>-on-call or something of the like, is it possible to have this sync up with our calendar? and better yet, github PR assignments? (spec-resyncs, dependabot, uv.lock update, etc etc) {color}
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for?
SERVER-137396Backlog
Add server-release as a codeowner on the v9.1 branch
server-release should be the codeowner on the v9.1 branch. See the changes made in SERVER-101869. Please also add server-release as a codeowner to src/third_party/wiredtiger/ to allow us to promote commits that were WT imports. See SERVER-117202 for an example of that change.
This depends on the DevProd "Build and Verification Branching Task", which should be linked to this ticket.
SERVER-96344Open
mongos doesn't honor a failpoint's full blockTimeMS
The behavior of {{MaxTimeMSExpired}} differs between mongod and mongos when using a blocking failpoint:
- mongod: Returns {{MaxTimeMSExpired}} after {{max(blockTimeMS, maxTimeMS)}}.
- mongos: Returns {{MaxTimeMSExpired}} after maxTimeMS only.
Repro: https://gist.github.com/prestonvasquez/d4b8193b4f67750994051ca61d8f035a
results for mongos:
results for mongod:
Failpoints should be uniform across topologies, behaving as mongod does. In particular, (for sharded clusters) drivers
Components
Testing Infrastructure
GODRIVER-3328Blocked
Make failpoints reliable in sharded clusters
h3. *Context*
Failpoints currently aren't reliable on sharded clusters for multiple reasons, including:
* {{mtest.SetFailPoint}} only sets a failpoint on one mongoS node by default. If a subsequent operation doesn't select the same mongoS, that can lead to non-deterministically failing tests because the failpoint isn't applied.
* mongoS doesn't block for the full duration specified by {{blockTimeMS}}. See SERVER-96344.
h3. *Definition of done*
* Set failpoint on every mongoS in sharded cl
Components
Testing
PYTHON-6283Blocked
Adopt shrub.py allowed_requesters support in the Evergreen config generator
h3. *Context*
PYTHON-6282 tracks the shrub.py fix for {{EvgTask}} dropping unknown keywords such as {{allowed_requesters}}. Two places in {{.evergreen/scripts/generate_config.py}} wait on it:
- {{backport-pr}} passes {{allowed_requesters=["commit"]}}; shrub.py drops it, so the generated task runs for any requester, patch builds included.
- The PYTHON-6178 review (PR #3215) split fuzzing into two variants because a single task cannot be kept off PR builds: PR builds run every task a pr-tag
Components
Infrastructure
SERVER-135655ClosedFixed
Shared lazily-initialized state in S2 classes allow data races
The S2 data structures {{S2EdgeIndex}} and {{S2Loop}} have {{mutable}} state that can be changed by {{const}} methods. Previously this was thought to be innocuous because it only affected integer counters. However, {{map}} and {{multimap}} data structures are also affected, which can result in a server crash when accessed concurrently.
* [S2Loop::vertext_to_index_|https://github.com/10gen/mongo/blob/efd5d7c5aa7dc2dfbed81dd081165cb4b3322e45/src/third_party/s2/s2loop.h#L333]
* [S2EdgeIndex::ma
Fixed Versions
9.1.0-rc08.3.169.0.78.0.377.0.489.1.0-rc1026
SERVER-134783In Code Review
Support live worker resize for the pipelined oplog applier
This ticket supports live worker resize: a runtime change to {{replWriterThreadCount}} (shared with classic) drains, restarts the pool, and resumes dispatch.
This ticket should include:
* On a {{replWriterThreadCount}} change: drain the pipeline, restart the {{PipelinedApplierWorkerPool}} with the new worker count, and resume dispatch.
* The pipeline is drained first, so no in-flight state remains at resize time.
Fixed Versions
9.1.0-rc09.1.0-rc1026
GODRIVER-4243Blocked
Change stream leaks the server cursor when Next's context expires or is canceled
When the context passed to {{ChangeStream.Next}} expires, the driver tries to resume using that expired context. The {{killCursors}} for the old cursor fails without being sent, but {{BatchCursor.Close}} sets the cursor ID to 0 anyway. A later {{{}ChangeStream.Close{}}}, even with a live context, therefore sends nothing. The server cursor stays open until the idle cursor reaper removes it.
Applications that bound each {{Next}} call with a timeout leak one server cursor per timeout. On deploym
GODRIVER-3024Backlog
Runtime Error 'index out of range' in MongoDB Go Driver ExtJSON Parsing
h3. Detailed steps to reproduce the problem?
_Include full traceback, if possible_
Reproducible with the following script:
Output:
h3. Definition of done: what must be done to consider the task complete?
An io.Reader should return io.EOF when the stack is exhuasted.
h3. The ex
Components
BSON & Extended JSON
GODRIVER-4260ClosedDeclined
mongo-go-driver - PR #2719: Merge release/2.10 into master
[mongodb-drivers-pr-bot[bot]|https://github.com/apps/mongodb-drivers-pr-bot] has created [PR #2719: Merge release/2.10 into master|https://github.com/mongodb/mongo-go-driver/pull/2719] in [mongo-go-driver|https://github.com/mongodb/mongo-go-driver]
SERVER-139496Needs Scheduling
S2 heuristic counters have incorrect behavior on overflow
Our S2 geospatial third party library uses {{int}} counters for heuristics, like for when the cost of building a data structure indexing polygon vertices is likely to be amortized.
* [S2Loop::num_find_vertex_calls_|https://github.com/10gen/mongo/blob/af22eb75e478f32fde03e16dfa748e4defa22055/src/third_party/s2/s2loop.h#L356]
* [S2EdgeIndex::query_count_|https://github.com/10gen/mongo/blob/af22eb75e478f32fde03e16dfa748e4defa22055/src/third_party/s2/s2edgeindex.h#L243]
For large collections
SERVER-137511ClosedDuplicate
Complete TODO listed in SERVER-123384
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/replicated_fast_count/replicated_fast_count_test_helpers.cpp:483
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-123384&type=Code
The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this
SERVER-139455ClosedFixed
Remove existence check in backports required for multiversion linter
This removes the requirement for entries in etc/backports_required_for_multiversion_tests.yml to match files on that branch.
Requiring existence for test files turned out to be too strict. It is common for a test to be renamed/relocated across backports, but the entry still needs to match the path used on master.
Components
Testing Infrastructure
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-126535Backlog
Comment field not propagated to shards in updateMany with pause-migrations flow
When a client attaches a {{comment}} to an {{update}} or {{delete}} command that triggers the pause-migrations coordinator path ({{_shardsvrCoordinateMultiUpdate}}), the {{comment}} field is silently dropped and never reaches the shard that executes the write. This means the comment never appears in the shard's slow query log, breaking user expectations and making cross-cluster observability difficult.
h2. Root Cause
In [coordinate_multi_update_util.cpp:135-139|https://github.com/mongodb/m
SERVER-139167Backlog
mongo shell segfaults (SIGSEGV, "Invalid access") running jstests/core/queryable_encryption/basic_crud.js on 8.0.35
h3. Summary
The {{mongo}} shell (8.0.35) crashed with SIGSEGV while running {{jstests/core/queryable_encryption/basic_crud.js}}. No stack trace file was produced, so the crash is unsymbolized.
Found in MongoDB CI for the mongosync (Cluster-to-Cluster Sync) project. The test runs against a replica set; replication and the cluster itself were healthy at the time.
h3. Log
resmoke recorded the test as exiting {{-11 (SIGSEGV)}}. Stack trace acquisition found nothing:
h3. What this is not
Th
SERVER-138002Investigating
Ensure long-running query spilling yields resources so global operations can make progress
h2. Problem
Long-running query spilling, spill-run consolidation, and recovery/merging of spilled state can execute inside a single stage/executor call while retaining locks or other execution resources. Where Global IS remains held, setUserWriteBlockMode may be unable to acquire Global X promptly. Queued Global X can also block new Global IS acquisitions and stall unrelated operations.
Interrupt checks alone do not release locks. Existing interrupt-delinquency fixes improve cancellation r
SERVER-139095In Code Review
Remove sbeFull parameter from getMinRequiredSbeCompatibility
{{getMinRequiredSbeCompatibility}} takes a redundant {{sbeFull}} parameter; every caller passes {{gFeatureFlagSbeFull.isEnabled()}} or a value that is always false.
* Read {{gFeatureFlagSbeFull}} inside the function instead.
* Drop the dead {{sbeFull}} parameter from {{shouldUseRegularSbeDeferredEngineSelection}}.
* No behavior change.
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139353Backlog
Add additional safeguards on inadvertent modification of Queryable Encryption safeContent tags
Currently, doing a direct update or findAndModify to an encrypted collection's {{__safeContent__}} array when {{bypassDocumentValidation}} is {{false}} is only prevented if the operation is a replacement-type update, or a {{$set}} on the {{__safeContent__}} field itself. It does not error if you try to {{$set}} a dotted path like {{__safeContent__.0}} or if you use other modifier-style update operation like {{$push}} or {{$pop}} on it.