Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
GODRIVER-4247Ready for Work
Audit CI build failures
h3. *Context*
Historical record for build failures is comprehensive.
h3. *Definition of done*
Need to put all build failures into one searchable type (build failure) and determine which build failures are still relevant in the CI.
h3. *Pitfalls*
Not investigated
Components
Evergreen
GODRIVER-4251Ready for Work
pydantic_core can't install on Windows
h3. *Name of Failure:*
pydantic-core can't be installed because it is marked as --no-build
h3. *Link to task:*
https://parsley.corp.mongodb.com/evergreen/mongo_go_driver_release_aws_auth_test__version~9.0_os_aws_auth~windows_64_2022_latest_small_aws_auth_test_a63b9e6fbc95eedb1da9897d30973a85e6b20c71_26_11_12_20_27_28/0/task?bookmarks=0,291
h3. *Context of when and why the failure occurred:*
Only fails on Windows "MONGODB-AWS Auth" tasks.
h3. *Stack trace:*
GODRIVER-4272Ready for Work
mongo-go-driver - PR #2726: Avoid quadratic parsing of trailing zeros in ParseDecimal128
[rajath201|https://github.com/rajath201] has created [PR #2726: Avoid quadratic parsing of trailing zeros in ParseDecimal128|https://github.com/mongodb/mongo-go-driver/pull/2726] in [mongo-go-driver|https://github.com/mongodb/mongo-go-driver]
SERVER-137393Backlog
Add new version to mongo-container project for 9.1
We need to add a new version to the mongo-container project to start publishing images for 9.1.
SERVER-137386Backlog
9.1 Build and Verification Branching Task
Follow the instructions for branching [on this README|https://github.com/10gen/mongo/blob/master/docs/branching/README.md]
SERVER-133481In Progress
Add isolated idLookup workload to dsi
Add a new Locust-based perf workload under {{workloads/query-execution/change-streams}} to benchmark the {{{}$_internalSearchIdLookup{}}}/ idLookup path. Given that internal search idLookup stage now builds on the same single-document lookup executor abstraction, this makes idLookup a good candidate for a dedicated perf workload under the existing change streams workload suite.
The goal is to establish a baseline for {{idLookup}} performance and make regressions easy to detect over time.
SERVER-139051ClosedFixed
Fix race in deprioritization_stats_and_observability.js currentOp priorityLowered check
h2. Problem
similar to a issue in [https://jira.mongodb.org/browse/SERVER-131934] we previously seen in delinquent_ops.js. deprioritization_stats_and_observability.js flakes in should report 'priorityLowered: true' in $currentOp while active.
The test waits for setPreYieldWait to be entered 3 times, then takes a single $currentOp snapshot and asserts priorityLowered: true. With batchSize: 3 and internalQueryExecYieldIterations: 1, those three pre-yield pauses are the entire find. The find
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139451In Code Review
Restrict the fixture dbHash rid opt-in to disagg until groupId membership lands
[{{replsettest.js}}|https://github.com/10gen/mongo/blob/20753a5d812/jstests/libs/replsettest.js#L2725-L2727] unconditionally passes {{includeReplicatedRecordIds: 1}} on every {{dbHash}} command. All fixture consistency checks funnel through it: {{checkReplicatedDataHashes}}, the [{{run_check_repl_dbhash.js}}|https://github.com/10gen/mongo/blob/20753a5d812/jstests/hooks/run_check_repl_dbhash.js] hooks (foreground, background, sharded), and initial-sync validation. The server [honors|https://githu
NODE-7901ClosedDone
Update dependencies for driver main
h3. AC
* Merge dependabot PRs that are safe to merge (semver-compatible updates, including any standalone package-lock-only PRs)
* When updating the dev dependencies to latest available semver compatible versions ANY reformatting MUST be done in a separate pull request and should ONLY be done if the team agrees that it is an important improvement
* Check dev dependency major version updates
** Update the major version if and ONLY if this can be done with minimal code changes; otherwise, file
Fixed Versions
7.9.1
NODE-5521Backlog
flaky: PlanExecutor error during aggregation :: caused by :: Error connecting to Search Index Management service. [13]
Search index test 4 fails.
https://spruce.mongodb.com/task/mongo_node_driver_next_rhel8_test_search_indexes_test_search_index_helpers_51a573fe99506b81c7ab808898eb9eb63f58f600_23_08_08_17_16_48/logs?execution=1
Components
Flaky Test
SERVER-138433In Code Review
Effective membership accessor + disagg sentinel
All functional predicates (oplog rid emission, applier rid honoring, rid-inclusive dbhash) and the hello/replSetGetStatus reporting surface need one cheap, unified membership value. Add {{getEffectiveRecordIdsGroupId(opCtx)}} (naming TBD), returning {{boost::optional<\{UUID, OpTime}>\}}:
- Attached storage: the persisted marker and cached it in memory. Loaded once at startup before replication starts. Updated transactionally at every mint, every clear, and initial-sync adoption. The cache must
SERVER-138106Open
Mint and announce the groupId at election (new-primary noop)
A groupless primary (feature flag on, latest FCV, attached storage) mints the {{groupId}} at election and announces it in the new-primary {{noop}}
h2. Details
- Mint: {{{}UUID::gen(){}}}; {{foundingOpTime}} is the new-primary noop's opTime. Both written in the same WUOW as the ([noop|https://github.com/10gen/mongo/blob/5fce3b99dea39b4f9453477819cedd935fba9a2c/src/mongo/db/repl/replication_coordinator_external_state_impl.cpp#L646]).
- Extend the noop payload with {{groupId}} and {{{}founding
SERVER-135570Open
Add observability for collections that have an absent collection hash
* Have counters with cumulative invalidations and record why we invalidated with the time, including prepared transactions and missing contributions (tbh this should be a very rare event after we support prepared txn, so there aren't many use cases where we would have an absent hash).
* Distinguish absent hashes from unsupported collections vs. collections that should be supported but aren't.
* Matching size/count with absent hashes must not count as a successful content-hash comparison (mak
SERVER-137736Open
Parse replicated metadata checkpoint only once
SERVER-137224 can be improved by
# Parsing the first op exactly once
# Parsing the checkpoint into a usable data structure within {{isCheckpointApplyOpsEntry()}}
Combine {{isCheckpointApplyOpsEntry()}} and {{parseCheckpoint()}} into a single function called {{{}tryParseCheckpoint(){}}}:
Record the checkpoint if it was parseable. Otherwise don't. This interacts with SERVER-136501, so do that first.
SERVER-136501Open
Handle checkpoint applyOps chain in parseCheckpoint()
See [comment|https://github.com/10gen/mongo/pull/63958#discussion_r4200143626]. The checkpoint parsing code does not currently parse chained applyOps for the replicated metadata checkpoint. The write is unlikely to be split because it requires 80k collection changes in a single checkpoint, but it falls within the upper bound of allowable collections.
See also [https://github.com/10gen/mongo/pull/65018#discussion_r4351536820.] This _should_ go away if we properly handle checkpoints split acros
SERVER-139004In Progress
Measure Phase 2 checkpoint validation duration
* Measure elapsed time for merge/expected-checkpoint computation and comparison, with the measured scope clearly documented.
* Expose invocation count and total duration; we may want to expose this as part of the Grafana dashboard.
GODRIVER-4182Backlog
Gate releases on a sensible list of pre-checks
h3. *Context*
Commit [14be9fb86|https://www.google.com/url?q=https://github.com/mongodb-labs/drivers-github-tools/commit/14be9fb86%23diff-c19011a32d4cf4f04a0089ef86511e3ce1c2493d4c25697e1625f27c7abf8a13R43&sa=D&source=docs&ust=1791321208473977&usg=AOvVaw3cGGFaaTzTDaXMgoPkH5O0] in github.com/mongodb-labs/drivers-github-tools fixed a typo in the secure-checkout/action.yml that was accidentally making it possible to checkout master in the golang/pre-publish action. While it was there, actions/ch
Components
Build
SERVER-125570ClosedFixed
Pushdown $match on keyHash into $queryStats stage to avoid full store scan
h2. Overview
The {{$queryStats}} aggregation stage currently performs a full linear scan of the in-memory query stats store on every invocation, regardless of any downstream {{$match}} predicates. Pipelines of the form
re-serialize the representative shape for every entry in the store and then discard most of them via the filter — wasted CPU proportional to store size, not result size.
h2. Background
Production clusters with many distinct query shapes have been observed running this pi
Fixed Versions
9.1.0-rc0
SERVER-135371ClosedFixed
Enable optimization query knob
Fixed Versions
9.1.0-rc09.1.0-rc1026
GODRIVER-3351Backlog
Create PR for interesting fuzz tests
h3. *Context*
The fuzz test is designed to fail whenever an interesting case is found, see [here|https://github.com/mongodb/mongo-go-driver/blob/32ff39b0f816d49e2a09b1059a8f741e59c75459/.evergreen/run-fuzz.sh#L72]. This causes confusion, since it is not actually a testing error but rather just an interesting case that we should add to the test corpus.
h3. *Definition of done*
Create a script similar to [backport-pr|https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.eve
Components
Testing