Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-134183ClosedFixed
Investigate: multi-statement transaction may read silently incomplete results after shard catalog history filtering
h3. Suspected problem
When {{featureFlagShardCatalogExpiredHistoryFiltering}} is enabled, authoritative metadata disk recovery drops chunk documents unless {{shard == <me>}} or {{onCurrentShardSince > <WT oldest timestamp>}} ( {{readCollectionMetadataFromDisk()}} in +[collection_metadata_synchronizer | [https://github.com/10gen/mongo/blob/master/src/mongo/db/shard_role/shard_catalog/collection_metadata_synchronizer.cpp#L37-L144]), and rebuilds the routing table with {{{}RoutingTableHistory::m
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-137928ClosedFixed
Add a microbenchmark for key_string::readValue()
The SBE hot path now uses readValue() instead of toBson(), so add a variant of the toBson benchmark that measures it.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-134424In Code Review
Remove the temporary disagg no-schema-epochs test variant
SERVER-133713 added enterprise-amazon-linux2023-arm64-disagg-no-schema-epochs, a temporary Evergreen variant that runs the disagg suite with featureFlagEnableSchemaEpochs set to false. It exists so a failure in the disagg suite can be attributed to schema epochs rather than to something else.
Remove the variant once schema epochs are stable enough that the comparison no longer earns its CI cost.
The variant is defined in etc/evergreen_yml_components/variants/amazon/test_dev_master_branch_only.
SERVER-81782ClosedFixed
Waiting for journalling is redundant with waiting for replication for replicated writes
See [this doc|https://docs.google.com/document/d/1TaN4VhYHU6Abpc2ccvAn65Sa9Im8ZtDymX7Ol6PwiJs/edit] for a more detailed description of how waiting for journaling works today.
Right now, for (implicit and explicit) {{j:1}} writes we wait for durability on the current node (which also includes waiting for no oplog holes if voters=1) prior to waiting for replication. However, the mechanism used for waiting for replication is redundant with the mechanism for waiting for durability now that the re
Fixed Versions
8.0.0-rc0
SERVER-139268ClosedFixed
Make SBE efficient boundary materialization flag an IFR
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138517Needs Scheduling
Disable test_api_version_compatibility
This task is not compatible with our BF infrastructure, security process, and breaks frequently with little value derived.
SERVER-123456ClosedGone away
Cleanup legacy classes for collection size and count
This [may include|https://github.com/mongodb/mongo/blob/6efa48969872ee9a29ed082b26e63c83ab6a6fe6/src/mongo/db/replicated_fast_count/replicated_fast_count_uncommitted_changes.h#L40], but is not limited to, {{UncommittedFastCountChange}}
SERVER-139208ClosedFixed
Refactor CheckpointHashValidationTest::appendCheckpoint()
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139190ClosedFixed
Refactor isRepairReplicatedMetadataO2()
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-137710ClosedFixed
Handle repair oplog entry in SizeCountCheckpointValidator
If we repair any replicated metadata for a collection, the standby must expect the repaired value(s). Without this change, we cannot repair any collection metadata while Phase 2 validation is enabled. There are at least a couple interesting cases:
# Repairing a {{boost::none}} hash to a real hash. If we parse the repair command correctly in the validator, we should be able to validate the collection’s hash during repair.
# Collection validation failed, so we are repairing incorrect metadata
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-136627Open
SBE ignores internalQueryLegacyDottedPathNullSemantics for MinKey/MaxKey comparisons on dotted paths through arrays
_Found by an AI bug hunt and confirmed by a differential oracle._
h2. Problem
For a comparison against {{MinKey}} or {{MaxKey}} on a dotted path that crosses arrays, the SBE engine returns the same documents whatever {{internalQueryLegacyDottedPathNullSemantics}} is set to, and differs from the classic engine under both settings. Comparisons against {{null}} agree between the engines under both settings.
h2. Repro
Collection {{c}} holds these documents; the query is run for each predicate belo
SERVER-139016Backlog
Use CompactHashAggStage for eligible $group stages behind featureFlagSbeCompactHashAgg
Make the SBE stage builder run an eligible scalar {{$group}} on {{CompactHashAggStage}}, behind {{featureFlagSbeCompactHashAgg}}, which stays off by default. The stage builder picks {{CompactHashAggStage}} only when all of these hold; otherwise it builds {{HashAggStage}} as before.
* {{featureFlagSbeCompactHashAgg}} is enabled.
* {{allowDiskUse}} is false, since the compact stage cannot spill yet.
* Every accumulator has a compact implementation ({{$sum}} and {{$push}} for now). A {{$group}} wit
Fixed Versions
9.1.0-rc09.1.0-rc1026
PYTHON-6167In Code Review
Split the test-non-standard task family into per-suite task families
h3. *Context*
{color:#505f79}The {{test-non-standard}} task family is shared by the encryption, load balancer, doctest, and PyOpenSSL suites, and the build variant decides which suite a task actually runs. Task names and tags do not identify the suite they run, which makes failures harder to attribute and keeps every suite from handling its own matrix.
PYTHON-6112 split the encryption runs by sync and async at the variant level. With per-suite task families, that mode belongs in the tasks
Components
Infrastructure
NODE-7905ClosedDone
Update dependencies for mongodb-connection-string-url
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
mongodb-connection-string-url-7.0.3
NODE-7906ClosedDone
Update dependencies for dbx-js-tools
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
SERVER-139333Needs Scheduling
Re-evaluate risk of zeroCE
After we have implemented histograms/NDV/MCV statistics, we should re-evaluate the risk of CE returning 0. And if its low, we should remove the fallback put into place by SERVER-136192/SERVER-136193
SERVER-139293In Progress
Incorrect output in $bucketAuto's $mergeObjects
In $bucketAuto's $mergeObjects, the value for each field should come from the document that is last in the input, tracked by its input position. When a value arrives, we compare its position with the largest position recorded for that field and only overwrite the output if it is greater. However, the recorded position is not updated when we overwrite the value. So the stored position stays at the first one seen for that field, and later values are compared against it instead of against the lates
SERVER-135420In Progress
Create PSAMEQueue, a single worker and PSAMEService
Create the PSAME task queue (a {{MultiProducerSingleConsumerQueue}}, producers use non-blocking {{tryPush()}}), a single worker thread running on low-priority tickets ({{TaskType::Background}}), and {{PSAMEService}} ({{ReplicaSetAwareService}}: {{onStartup}} initializes the queue and worker; {{onStepUpComplete}}/{{onStepDown}} notify primary state). {{PSAMEService}} is instantiated in {{mongod_main.cpp}}'s {{_initAndListen}}.
The queue has a single consumer, so there is one worker, not a pool.
SERVER-134963In Code Review
Lower the number of initial sync attempts before crashing
Based on an investigation into how many attempts an initial sync node requires before succeeding, 99.677% of initial syncing nodes succeed after 0 or 1 retries. Out of 83,323 initial sync attempts, only 5 initial syncs failed the first three attempts and succeeded on some later attempt (4-9).
As a result, it seems we can safely lower the initial sync attempt threshold. 10 seems to be too large of a number and we can increase observability by failing sooner.
SERVER-137247ClosedDone
Prototype a Query Admission Control and run against OOM reproducers
Help us to evaluate the impact of QAC for OOM reproducers.