Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139343Backlog
Add batch buffering for WiredTiger SortedDataKeyValueView cursors
Implement batch buffering for WiredTiger SortedDataKeyValueView cursors, which will buffer the views and return from the buffer until the buffered batch is exhausted or invalidated.
SERVER-139341Backlog
Add batch buffering for WiredTiger record store cursors
The implementation of WiredTigerRecordStoreCursor should internally buffer up to `maxBatch` when `next` is called on that cursor. Records should be returned from that batch until it is exhausted or invalidated.
NODE-8000Investigating
Improve node driver perf testing
h3. Use Case
As a... _(who is this for)_
I want... _(what is the desired change)_
So that... _(why is the change desired)_
h3. User Experience
* _What is the desired/expected outcome for the user once this ticket is implemented?_
* _If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?_
h3. Dependencies
* _upstream and/or downstream requirements and timelines to bear in mind_
h3. Risks/Unknowns
* _What could go wrong while im
SERVER-96874ClosedFixed
Replication recovery can crash due to concurrent shutdown
In the linked AF ticket, the node was [applying oplog entries|https://github.com/10gen/mongo/blob/09d253d066bb41ef298ac79ec581ccee3bfc250c/src/mongo/db/repl/replication_recovery.cpp#L792-L811] as part of replication recovery as a standalone. There was a concurrent shutdown triggered by a SIGTERM and then the node [crashed|https://github.com/10gen/mongo/blob/09d253d066bb41ef298ac79ec581ccee3bfc250c/src/mongo/db/repl/replication_recovery.cpp#L534-L536] since shutdown [kills all operations|https://
Fixed Versions
9.0.0-rc08.3.98.0.377.0.49
SERVER-104325ClosedFixed
[v8.0] DDL lock acquisition can hang indefinitely on secondaries
The {{setAlwaysInterruptAtStepDownOrUp_UNSAFE()}} function on the operation context is unsafe in a sense that if a stepdown happens during the run of that function, the said stepdown (and the interruption) would be missed.
If a component tries to acquire the DDL lock after it became a secondary, it will hang for 5 minutes (the default timeout for the DDL lock acquire) since the DDL lock acquisition waits for the recovery of the {{{}ShardingDDLCoordinator{}}}, what will never happen because th
Affected Versions
7.0.08.0.0
Fixed Versions
8.0.167.0.49
SERVER-125921ClosedFixed
Sharded timeseries collMod can abort without releasing participant critical sections
A sharded time-series {{collMod}} can leave shard participant critical sections held if it hits a non-retriable error after the {{kBlockShards}} phase.
{{CollModCoordinator}} enters the critical section in {{kBlockShards}} by sending {{_shardsvrParticipantBlock}} with {{ReadsAndWrites}} to shards owning chunks. It only releases that critical section later as a side effect of {{_shardsvrCollModParticipant}} in {{{}kUpdateShards{}}}, when the participant sees {{needsUnblock=true}} and calls {{{
Affected Versions
7.0.08.0.09.0.0-rc08.3.0
Fixed Versions
9.1.0-rc09.0.48.3.168.0.377.0.49
SERVER-132463ClosedFixed
Clustered Index names allow null embedded bytes
Discovered via the fuzzer. Attaching a minimal reproducer. I would recommend updating the up-front validation of clustered index names.
One of the problems with storing embedded null bytes in an index name is that collStats cannot represent the name in BSON since SERVER-95279 introduced stronger checks in the server.
Affected Versions
9.0 Required
Fixed Versions
9.1.0-rc08.3.99.0.0-rc28.0.377.0.49
SERVER-132638ClosedFixed
count with limit 0 fails on a view but works on a collection
For the {{count}} command {{limit: 0}} means no limit, and on a collection it returns the full count. The same command against a view returns error 15958, "the limit must be positive".
Negative limits are not affected. {{limit: -1}} on a view returns 1, which matches the collection, so zero is the only value that differs.
Every way of writing zero gives the error, so it does not depend on the numeric type. {{{}0{}}}, {{{}0.0{}}}, {{{}-0.0{}}}, {{NumberDecimal("0")}} and {{NumberDecimal("-0
Affected Versions
8.2.47.0.318.2.68.2.12
Fixed Versions
9.1.0-rc09.1.0-rc10229.0.48.3.168.0.377.0.49
SERVER-136184ClosedFixed
Require release Evergreen distros when the Bazel build wrapper uses release configurations
h2. Problem
The Evergreen Bazel build wrapper can enable release configurations while running on a regular Evergreen distro. During review of [mongo PR #63636|https://github.com/10gen/mongo/pull/63636], s390x release compilation was moved to ARM64 builders, but the assignments used regular distros despite equivalent release distros being available. Add a runtime check to catch this configuration mistake before compilation.
h2. Proposed change
Add a shared check to {{evergreen/bazel_compile.sh}}
Components
Bazel
Fixed Versions
9.1.0-rc09.1.0-rc10248.3.169.0.78.0.377.0.49
SERVER-121207ClosedFixed
tassert in plan enumerator when empty path and $elemMatch are used
The repro script attached reaches a tassert in the plan enumerator, "9074700: RelevantTag is not assigned to the match expression node". From what I've tried, the empty path + elemMatch seem to be required to reach this issue
Fixed Versions
9.0.0-rc08.0.377.0.498.3.18
SERVER-136176ClosedFixed
Backport cross compile for zseries machines
Fixed Versions
8.3.169.0.78.0.377.0.49
SERVER-137799ClosedFixed
Preserve release binary hashes across RPM and DEB packages
RPM postprocessing can rewrite ELF symbol metadata in already finalized release binaries, making the installed binaries differ from the release tarball. Disable RPM stripping across community and enterprise package specs so packaging preserves the original bytes.
Release package tests now compare the SHA-256 hashes of installed {{mongod}} and {{mongos}} with the hashes verified against the release archive, before invoking either binary. The checks use the existing provenance eligibility and ski
Components
Packaging
Fixed Versions
9.1.0-rc09.1.0-rc10257.0.499.0.98.3.188.0.39
SERVER-138692In Code Review
Verify macos notary client binary checksums and signatures in Server Repo before execution
Fixed Versions
9.1.0-rc09.1.0-rc10257.0.499.0.98.3.188.0.39
SERVER-139040In Progress
Use high-memory r8g hosts for RHEL 8.8 ARM64 release compilation
h2. Problem
[BF-47163|https://jira.mongodb.org/browse/BF-47163] tracks repeated {{archive_dist_test}} failures on {{enterprise-rhel-83-s390x}} in {{mongodb-mongo-v9.0-staging}}. The Bazel JVM was OOM-killed on the {{release-rhel8.8-arm64-m8g-4xlarge}} cross-compile host. Increasing the timeout alone cannot fix peak memory exhaustion.
h2. Change
Use the newly created high-memory host pair for the RHEL 8.8 ARM64 release compile tasks and their corresponding non-release compile tasks:
* {{release-
Fixed Versions
7.0.499.0.98.3.188.0.39
SERVER-137594ClosedFixed
remove curatorbin reference in mongo codebase
DevProd was asked to archive the curatorbin repo; I looked for references and I was able to find one in [10gen/mongo|https://github.com/10gen/mongo/blob/c4c92c46217cbca658c4f6f6e88d050dbf9f4179/pyproject.toml#L238] and [mongodb/mongo|https://github.com/mongodb/mongo/blob/master/pyproject.toml#L238]. This should be cleaned up since its unused and the repo is now archived.
Assigning to Build given codeownership.
Fixed Versions
9.1.0-rc07.0.499.0.98.3.188.0.39
SERVER-139196ClosedFixed
Defer package provenance type annotations for Python 3.9 compatibility
h2. Problem
The v7.0 staging package-test driver fails during import on hosts using Python 3.9.2. Type annotations in {{buildscripts/package_test_provenance.py}} are evaluated at module import time; the PEP 604 union expression {{Path | None}} requires Python 3.10 unless annotations are postponed.
The failure happens before any package installation or package tests run. The representative RHEL 8 task reports zero test results.
h2. Observed failure
[Waterfall build|https://spruce.corp.mongodb.c
Fixed Versions
7.0.49
SERVER-139334In Code Review
Fix Python dependency compatibility in v7.0 package tests
h2. Problem
The {{test_packages}} task on {{mongodb-mongo-v7.0-staging}} fails during Python dependency installation. The task uses Python 3.9, but the pinned {{types-PyYAML==6.0.12.20261103}} release requires Python >= 3.10.
This prevents package tests from running on multiple v7.0 build variants. See [BF-47214|https://jira.mongodb.org/browse/BF-47214] and the [failing suse12 task|https://spruce.mongodb.com/task/mongodb_mongo_v7.0_staging_suse12_test_packages_d481c335222d9536640aff825ac47da2
Fixed Versions
7.0.49
SERVER-139185ClosedFixed
v7.0 lint-pylinters task fails for unchanged files
Components
Testing Infrastructure
Fixed Versions
7.0.49
NODE-7904Needs Verification
Update dependencies for mongo-client-encryption
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