Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-136690ClosedFixed
Complete TODO listed in SERVER-130178
There is a TODO in the codebase referencing a resolved ticket which is assigned to you.
Please follow this link to see the lines of code referencing this resolved ticket:
https://github.com/10gen/mongo/search?q=SERVER-130178&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 ticket to represent the work you're actually doing.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136213ClosedFixed
Prevent interrupt delinquency inside $group spill merge iterations and the pre-spill sort
h2. Overview
Follow-up to SERVER-136021 (PR #63654). SERVER-136021 bounded the check-free spans *between* spill-write iterations and merge iterations in the $group spill paths. Workloads with large accumulator state (e.g. large $push arrays) still show interrupt-check delinquency because large check-free spans remain *inside* a single merge iteration and inside the pre-spill in-memory sort. These delay kill processing and keep the operations marked interrupt-delinquent.
Note: teardown/dealloca
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136917ClosedFixed
Skip writing QS entries that fail bson validation into the store
There are a class of QS entries that [QueryStatsStage::toDocument(...) skips outputting|https://github.com/10gen/mongo/blob/08ca0098282d41e26c46eeda7aa0d5e0fee647fe/src/mongo/db/exec/agg/query_stats_stage.cpp#L239-L275] because they violate certain BSON validation constraints. Since we know whether a QS entry will violate said constraints at write-time, we can explicitly avoid writing those entries to the store.
Perhaps this can also be extended to the other checks that lead to skipping entr
Fixed Versions
9.1.0-rc09.1.0-rc1025
JAVA-6355Execution Blocked
Deterministic locality-aware mongos selection for multi-region sharded clusters
This ticket was split from {{DRIVERS-3604}}, please see that ticket for a detailed description.
PYTHON-6202Execution Blocked
Deterministic locality-aware mongos selection for multi-region sharded clusters
This ticket was split from {{DRIVERS-3604}}, please see that ticket for a detailed description.
CSHARP-6286Execution Blocked
Deterministic locality-aware mongos selection for multi-region sharded clusters
This ticket was split from {{DRIVERS-3604}}, please see that ticket for a detailed description.
GODRIVER-4218Execution Blocked
Deterministic locality-aware mongos selection for multi-region sharded clusters
This ticket was split from {{DRIVERS-3604}}, please see that ticket for a detailed description.
SERVER-137585ClosedFixed
Add restartable task-owned artifact uploader
Adds `buildscripts/task_artifacts.py` and Evergreen’s `upload task artifact` function as a replacement for `s3.put` for task artifacts. It provides task prefixes, conditional writes, restart support, validated filenames and content types, matching visibility/ACLs, download-only headers, Intelligent-Tiering, and signed artifact links. Adoption requires migrating upload configurations; existing producers retain their current uploads until the next PR. The migration updates both artifact producers
Components
buildscripts
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137565ClosedFixed
Remove featureFlagContainerWrites from fully disabled list
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-114032ClosedFixed
Avoid obscuring network errors in OplogFetcher
In [{{OplogFetcher::_checkTooStaleToSyncFromSource}}|https://github.com/10gen/mongo/blob/d14e3cc6183dddc97aac5393fcc085f25a1d4d7f/src/mongo/db/repl/oplog_fetcher.cpp#L1034-L1044], all raised execptions in this try/catch block are treated as treated as "too stale to sync from source" errors, even network errors, leading to the stall seen in HELP-83793. Instead, we should likely both log the error message itself and return {{{}ErrorCodes::OplogStartMissing{}}}, as we do at the end of the function
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-127796ClosedFixed
Server status metric to track aggregation queries running without holding execution tickets
Add an appropriate server status metric (or multiple metrics) allowing us to attribute outages the lack of SPM-4302. That is, track agg queries that are still executing after having released their storage tickets. Such queries do not participate in execution control.
This should include:
* Counting query instances that run for more than 30ms after releasing their storage ticket(s).
* Tracking the total "non-ticketed" execution time across all such cases.
Fixed Versions
9.0.0-rc1
SERVER-130362ClosedFixed
agg_non_ticketed_metrics.js assertion failures
Two test-only issues in agg_non_ticketed_metrics.js:
# with internalQueryFrameworkControl: "forceClassicEngine"[jstests/noPassthrough/query/server_status/agg_non_ticketed_metrics.js:76|https://github.com/10gen/mongo/blob/1c5341006ae2bc955ff69e85e81111e3bebfcefe/jstests/noPassthrough/query/server_status/agg_non_ticketed_metrics.js#L76] assert can fail. The sleepAfterReleasingAggTicket failpoint used mode: "alwaysOn", assuming the aggregate releases its execution ticket exactly once. DocumentSou
Fixed Versions
9.0.0-rc1
SERVER-136487ClosedFixed
Make a warning in validate when a collection is eligible to have a collection hash but it isn't present
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-131547ClosedFixed
INLJ costing depends on syntactic join-edge order
For transitive multi-table joins, INLJ enumeration costs only {{{}edges[0]{}}}. Edge order follows query syntax, so equivalent queries may use different selectivity estimates and choose different plans/costs.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138154ClosedFixed
Fix disagg change stream preimages test
This change fixes the test
{{jstests/noPassthrough/query/change_streams/tenant_preimages.js}} in the {{no_passthrough_disagg_override_replsets}} test suite.
A previous change from SERVER-137822 added a new test that caused a tripwire assertion in the secondary oplog application. This caused BF-46996.
This change fixes the failure, by disabling replicated recordIDs in the newly added test.
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138078ClosedIncomplete
Investigate linear growth of TopologyDescription in Atlas cluster
In [this report|https://pages.monglify.aix.prod.corp.mongodb.com/p/rampart-wizard-napkin] derived from the linked HELP ticket, we see linear growth of {{TopologyDescription}} over time. We'd like to know why this is happening.
The report was generated from shard 00-02, on the mongos.
In order of priority:
# Is this a leak related to SERVER-135020? My initial judgement says no, but it's possible.
# Do we need to change any log verbosity components on the server to find out more? We need t
CSHARP-6281ClosedFixed
NoSQL command injection via mismatched raw BSON length prefix written verbatim to the wire (backport to main)
Fixed Versions
4.0.0
CSHARP-6282ClosedFixed
BSON output corruption via out-of-range binary subtype bypassing UUID and OldBinary guards (backport to main)
Fixed Versions
4.0.0
NODE-7951Blocked
Support AKS Workload Identity for Automatic KMS Credentials
This ticket was split from {{DRIVERS-3468}}, please see that ticket for a detailed description.
Components
Client Side Encryption
JAVA-6353Blocked
Support AKS Workload Identity for Automatic KMS Credentials
This ticket was split from {{DRIVERS-3468}}, please see that ticket for a detailed description.
Components
Client Side Encryption