Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138881ClosedFixed
IntentRegistry::_totalOpsKilled may be accessed without the lock
See https://github.com/10gen/mongo/blob/eac9038fbdb25fd726a0d3ccd1a6f432ba6b5b6b/src/mongo/db/repl/intent_registry.cpp#L651-L653.
Suggested remedy is to use the {{MONGO_LOCKING}} annotations to prove that the lock is held when it should be. An AI implementation is [here|https://github.com/10gen/mongo/compare/brad.cater/tmp-ir-checked?expand=1].
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137926Open
Write decision doc following TLA+ of proposed changes
Write a doc explaining the proposed changes and showing the findings from modeling those changes using TLA+.
SERVER-139137In Progress
Estimate NDVs within samples to handle zero CE cases on equality predicates
Supplement {{CardinalityEstimator::clampZeroEstimate}} with a more intelligent heuristic, for equality predicates in particular, since these can be effectively estimated from NDV and we can estimate NDV from the sample. Run a Chao1 estimator for distinct value estimation on the sample (or choose an alternative NDV estimator). Then calculate the equality predicate's CE as {{{}1/NDV{}}}.
JAVA-6258In Progress
Support arbitrary aggregate command options in ChangeStreamIterable/Publisher, AggregateIterable/Publisher
h2. Support CustomOptions on ChangeStreamOptions and AggregateOptions
Many of our customers on MongoDB 7 and lower have kafka related workflows that connect and read directly from a shard. MongoDB 8 prevents this, but the custom option $_passthroughToShard allows for this. Furthermore, the mongodb kafka connector is built on Java, and without these custom options, the connector is unable to directly read from a shard in MongoDB 8+
Components
AggregationChange StreamsCRUD
SERVER-137300Needs Merge
Register and run extension commands
Add {{register_command_descriptor}} to the host portal vtable in {{api.h}}, gated on 1.1. Implement it in the host portal adapter, and add the SDK registration helper. Add the {{ExtensionCommand}} host bridge. Register the command in every role it declares, including registries built after the extension loads. Map all static properties onto the matching {{Command}} overrides, including enforcing {{requiredPrivileges}} in {{checkAuthForOperation}}. Pass a namespace-only command context; SERVER-13
SERVER-139132ClosedFixed
Fix flaky resume token advancement test
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139143Needs Scheduling
Add sharded-cluster EOT txn FSM coverage (gated on router-side synthesis)
Extend the EOT txn FSM suite \(SERVER\-139142\) to sharded clusters with endOfTransaction ENABLED, plus the sharded\-only resume/IRS signals. Gated: requires router\-side EOT synthesis for prepared multi\-shard txns \(SPM\-4826 milestones\) and the framework's sharding setup work to settle.
h2. Scope of Work
\* Sharded matrix rows with showEndOfTransaction whenAvailable/required \(the off rows already ship with SERVER\-139142\).
\* C3 kickback: a stream starting inside a txn commit\-span stradd
SERVER-139142Needs Scheduling
Add end-to-end EOT txn FSM test suite (replica set) with matrix suite wiring
Add the end\-to\-end change stream FSM suite verifying the endOfTransaction event \(SPM\-4826\) on replica sets: prediction per watch mode and reader mode, the gating matrix and equivalence, multi\-writer interleave, and resume flavors. Each test builds its own cluster \(nodb suite\).
h2. Scope of Work
\* Create {{jstests/libs/util/change\_stream/change\_stream\_txn\_utils.js}} — {{setupTxnFsmCluster}} \(RS branch; {{kEotMongodParameters}} flag chain incl. {{allowEndOfTransaction}} override; no
SERVER-128731ClosedFixed
Extend checkValidation disambiguation further into validateBucketConsistency results
Fixed Versions
9.1.0-rc0
SERVER-136876ClosedFixed
$graphLookup $_internalFromPipeline should not be allowed in in view definitions
That field is only allowed by internal clients, it should not be allowed in view definitions. The fact that it's allowed in view definitions can be abused to read collections that the user is not authorized to read.
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.7
SERVER-136505ClosedFixed
Use-after-free in strict time-series bucket validation via stale FlatBSON field lookup map
h2. Problem
The strict time-series bucket validator, which runs by default on raw bucket inserts and updates ([validateBucketConsistency|https://github.com/10gen/mongo/blob/f18a6b6768b/src/mongo/db/timeseries/timeseries_bucket_validation.cpp#L481-L560], dispatched from [CollectionImpl::checkValidation|https://github.com/10gen/mongo/blob/f18a6b6768b/src/mongo/db/shard_role/shard_catalog/collection_impl.cpp#L606-L621]), rebuilds a bucket's min/max summaries by merging every measurement value in
Affected Versions
8.3.38.3.48.3.58.2.128.3.68.2.138.0.288.3.78.0.298.3.88.3.99.0.09.0.19.0.29.0.39.0.49.0.5
Fixed Versions
9.1.0-rc09.1.0-rc10258.3.169.0.78.0.377.0.48
SERVER-131412ClosedFixed
improve Validation Expression
Fixed Versions
9.1.0-rc08.0.348.3.139.0.4
SERVER-138242Open
Retire the per-collection recordIdsReplicated option
Set-wide Replicated RecordIds (SPM-4519) makes rid replication node state (flag + FCV + membership), not a collection property. Remove the per-collection recordIdsReplicated option from the write and catalog paths.
h2. Details
- Stop writing it: new collections never persist the field, create oplog entries stop carrying it ([onCreateCollection|https://github.com/10gen/mongo/blob/5fce3b99dea39b4f9453477819cedd935fba9a2c/src/mongo/db/op_observer/op_observer_impl.cpp#L1844], including the SER
SERVER-138919ClosedGone away
Complete TODO listed in SERVER-134962
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/replicated_fast_count/replicated_fast_count_advance_checkpoint.h:82
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-134962&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 th
SERVER-137869In Progress
Update analyze to respect collMod sample size settings
Analyze should use the sample sizes set by collMod for the source collection to determine how many docs to sample. If that attribute is not set, then use the existing query knobs.
Analyze should generate 1 sample that can fulfill both JOO and CBR's needs.
SERVER-138590ClosedFixed
Complete TODO listed in SERVER-138116
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* jstests/replsets/index_builds/rollback_index_build_attempts.js:128
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-138116&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 r
Components
Testing Infrastructure
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139134Investigating
Include etc/evergreen_main_staging_poc.yml in the archive_dist_test tarball
h2. Problem
Follow\-up to SERVER\-138693. Tasks on the {{mongodb\-main\-staging\-poc}} project that run from the dist\-test archive fail in the {{determine task timeout}} step:
The file exists on the branch and {{evergreen\_config\_file\_path}} points at it, but the archive built by {{archive\_dist\_test}} only includes an explicit allowlist of {{src/etc/}} files \({{evergreen.yml}}, {{evergreen\_nightly.yml}}, {{evergreen\_timeouts.yml}}, ...\), so the new file is missing from the tarball.
GODRIVER-4169ClosedFixed
Client.BulkWrite drops top-level errors and partial results, violating CRUD spec "Top-Level Errors"
h3. *Context*
The CRUD Bulk Write [spec|https://github.com/mongodb/specifications/blob/master/source/crud/bulk-write.md#top-level-errors] requires:
{quote}When a top-level error is encountered and individual results and/or errors have already been observed, drivers MUST embed the top-level error within a BulkWriteException as the error field to retain this information.
{quote}
{{clientBulkWrite.execute}} does not do this for command errors (\{ ok: 0 }). mongo/client_bulk_write.go:98-107 ma
Components
CRUD
Fixed Versions
2.10.1
SERVER-78918ClosedFixed
Make `shardCollection` command shard authoritative
Currently, the shadCollection command is doing a best effort to inform involved shards about the new collection that they own. The goal of this ticket is to make shardCollection command shard authoritative, in order that, all shard will know about the filtering information that they own before serving any type of operation.
h4. Documentation
[Technical Design|https://docs.google.com/document/d/1C0PlrI1nQYxS9mREPN3iBXsWaFJS27M_YNjJT-n7Tgk/edit#heading=h.nb59t8rn029k]
Components
Sharding
Fixed Versions
7.3.0-rc0