Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139370ClosedFixed
bucketAuto mergeObjects charges only retained data
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-129240Open
Unify/rename SamplingCEMethodEnum and SamplingTechnique enum
SamplingCEMethodEnum (used by internalQuerySamplingCEMethod knob) only includes chunk and random sampling, while SamplingTechniqueEnum contains all the possible actual sampling methods (chunk, random, full coll scan, sequential scan, and strides) including the test-only methods.
This is increasingly confusing to work with, so we should either decide on different naming that better describes why there are two separate groups, or somehow unify these into one enum that includes everything we nee
SERVER-138126In Code Review
Re-key dbhash includeReplicatedRecordIds to the in-scope predicate
dbhash's opt-in {{rid}} hashing ([includeReplicatedRecordIds|https://github.com/10gen/mongo/blob/5fce3b99dea39b4f9453477819cedd935fba9a2c/src/mongo/db/commands/dbhash.cpp#L67]) currently keys on the per-collection recordIdsReplicated option. When the caller opts in with that flag, re-key the predicate to the shared in-scope predicate, so the
cross-node rid-match oracle actually includes {{rids}} once the per-collection option stops being written.
h2. Details
- Without this, the opt-in predi
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-117561Open
Drop the overrideRecordIdsReplicatedFalse failpoint from dbcheck_logs_minkey_maxkey.js
[{{dbcheck_logs_minkey_maxkey.js}}|https://github.com/10gen/mongo/blob/20753a5d812/jstests/replsets/dbcheck/dbcheck_logs_minkey_maxkey.js] writes to the secondary in standalone mode to introduce corruption, then asserts dbCheck's health log catches it with the expected minKey/maxKey entries. It was exempted from rid-enabled collections via [{{overrideRecordIdsReplicatedFalse}}|https://github.com/10gen/mongo/blob/20753a5d812/jstests/replsets/dbcheck/dbcheck_logs_minkey_maxkey.js#L38] as the exped
SERVER-138124Open
Membership-based recordId emission and honoring in the oplog path
Flip both ends of the {{rid}} pipeline from the per-collection {{recordIdsReplicated}} catalog option to {{groupId}} membership in one commit: a primary emits rids iff it holds a {{groupId}}, and an applier honors them iff it holds a {{groupId}}.
h2. Details
- Emission: the op observer already sets the {{rid}} ([oplogEntry.setRecordId in op_observer_impl.cpp|https://github.com/10gen/mongo/blob/5fce3b99dea39b4f9453477819cedd935fba9a2c/src/mongo/db/op_observer/op_observer_impl.cpp#L811]). The
SERVER-138309Open
Clear the groupId on standalone document-data writes (C4)
Standalone inserts diverge the rid space, so they must clear the groupId. Decided design: clear at the first standalone insert into an in-scope collection, plus storage-level record store rebuilds. Only new rid assignment can create a wrong rid-to-document mapping: updates are in-place and never change a rid, deletes create missing mappings but never wrong ones. Rolling Index Builds and read-only standalone maintenance (including TTL deletes) preserve membership.
h2. Details
- A one-shot gua
SERVER-138186Open
TTL resume skips owned documents that share an index key with more than ttlIndexDeleteTargetDocs unowned documents
After SERVER-92779, a batched TTL delete on a secondary index resumes from the index key of the last staged document. If an attempt stages only entries equal to that key and deletes none of them, the next attempt starts after the key, because SortedDataInterface::Cursor cannot seek to a (key, RecordId) position. Owned expired documents that share that exact key and sort after the first {{ttlIndexDeleteTargetDocs}} unowned documents by RecordId are skipped for the rest of the pass. Every pass rep
SERVER-136713Needs Merge
Add testing for index builds on edge case documents
An idea that has come up repeatedly is to create a corpus of edge case BSON documents that we can use for deterministically testing the database. The linked BF is an example where that could have helped, as empty array vs sub-document is a known cause of subtle issues. Other examples would be very large documents, very large keys, very many keys, different geo data formats, very deeply nested documents, strings with non-UTF8 contents. We would want all BSON types, including deprecated (but allow
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139146ClosedFixed
transaction_aborted_under_cache_pressure.js sets CachePressureAbortSessionKillLimitPerBatch at runtime, triggering a ThreadSanitizer data race
Description:
h3. Problem
jstests/noPassthrough/txns_cache_errors/transaction_aborted_under_cache_pressure.js fails deterministically on the ThreadSanitizer variant (enterprise-rhel8-debug-tsan). The test sets CachePressureAbortSessionKillLimitPerBatch via a runtime setParameter, which races with the periodic rollbackUnderCachePressure thread reading the same global. TSAN aborts the server, the connection drops, and the test fails at load:
Reproduced on v8.3 patch 4213 (13/13 runs fa
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139415ClosedFixed
Fix MongoShellProgramSkipExtensionsSignatureVerificationTestCase setup of config defaults
Test case class MongoShellProgramSkipExtensionsSignatureVerificationTestCase directly modifies module level variables in module `buildscripts.resmokelib.config`.
The values are not restored at teardown, thus breaking the isolation of each test.
The purpose of this ticket is to modify the testcase so that it uses a context manager to modify the value, and to limit the change only to the variables which are actually needed.
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139505Needs Scheduling
Store genId as a metadata field in persistent sample docs
Currently genId is only stored in a sample's _id, not in the metadata fields on each page. For ease of filtering $persistedStats output it would be nice to represent as a metadata field.
SERVER-136023ClosedWon't Do
Prevent interrupt delinquency in $facet and $lookup by checking for interrupt in the sub-pipeline drain loops
$facet and $lookup each run entire sub-pipeline executions inside one {{doGetNext()}} call. Sub-pipeline stages check interrupts every 128 {{getNext()}} calls via {{Stage::getNext}} -> {{{}ExpressionContext::InterruptChecker{}}}, but (a) sub-pipelines processing fewer than 128 docs may never trip the amortized checker (each sub-pipeline has its own {{ExpressionContext}} counter), (b) per-input plan build/optimize/translate cost is check-free, and (c) blocking sub-stages expose their full span in
SERVER-139188In Code Review
Implement type narrowing for the remaining comparisons expressions
Follow up from SERVER-135984. After $eq works, the logic should be expanded to: $lt, $lte, $gt, $gte, $ne. Not $cmp - it will not be supported and it returns a number.
$lt:["$a", "string"] constrains 'a' to be of the type string and types that sort before string. Should probably look like 'minKey|missing|null|undefined|number|string'.
$ne does nothing unless the type is a singleton type - $ne: ["$a", "string"] cannot tell us the type of "a" but a != null can tell us it's not null.
Fixed Versions
9.1.0-rc09.1.0-rc1026
PYTHON-6282In Code Review
shrub.py silently drops allowed_requesters from task definitions
h3. Detailed steps to reproduce the problem?
Pass a documented Evergreen task field to {{shrub.v3.evg_task.EvgTask}} that the model does not declare, for example {{allowed_requesters}}:
Output with shrub.py 3.11.0 and pydantic 2.14.3:
The constructor accepts the keyword, pydantic drops it because the model ignores extra fields, and no error surfaces. The field never reaches the generated YAML.
h3. Impact
Configurations that set {{allowed_requesters}} on a task silently los
Components
Infrastructure
SERVER-41263ClosedFixed
Disallow the empty string as an index key type
At present it is possible to generate an index with an empty string as the key type (eg a definition of \{x:""}). The optimizer seems to be able to use this index when the key is a predicate in the query:
However it is unable to use the index to sort:
{noformat}
> db.repro.find({x:123}).sort({x:1}).explain()
{
"queryPlanner" : {
"plannerVersion" : 1,
"namespace" : "repro.repro",
"indexFilterSet" : false,
"parsedQuery" : {
"x" : {
"$eq" : 123
}
},
"que
Components
Index Maintenance
Fixed Versions
4.3.14.2.3
SERVER-96766ClosedFixed
Verify behavior of pre-3.4 index key specs on 3.4+ versions
*Background*
The server only applies stricter index key pattern validation to v:2 indexes (as of SERVER-26659). This means that the server does not apply stricter validation on pre-3.4 legacy indexes. Pre-3.4 index key values could be 0, empty string, numbers other than -1 and 1, non-numeric / string values, etc. See SERVER-11064 for more information. 3.4+ server versions still handle pre-3.4 legacy indexes because these legacy indexes can persist across server upgrades.
*Solution*
We shoul
Fixed Versions
8.1.0-rc0
SERVER-137418In Code Review
Add pre-condition/post-conditions infrastructure for Resharding Recipient
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-137254Investigating
Call SBE fetch index key checks directly instead of via callbacks
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139504Needs Scheduling
Drop the overrideRecordIdsReplicatedFalse failpoint from index_downgrade_fcv.js
[{{index_downgrade_fcv.js}}|https://github.com/10gen/mongo/blob/20753a5d812/jstests/multiVersion/genericSetFCVUsage/index_builds/index_downgrade_fcv.js] verifies that a downgrade attempted with an index build in progress fails cleanly before doing any work. It [enables|https://github.com/10gen/mongo/blob/20753a5d812/jstests/multiVersion/genericSetFCVUsage/index_builds/index_downgrade_fcv.js#L24 {{overrideRecordIdsReplicatedFalse}} for the whole run so collections are created without {{recordIdsR