Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138107ClosedFixed
[POA] Dispatcher may pipeline truncateRange oplog entry when it shouldn't
The POA dispatcher, on receiving a batch from the OplogApplierBatcher, tries to decide whether the batch should be serialized or pipelined. It does this by inspecting the oplog entries of the batch and then runs OplogApplierBatcher's [{{getBatchActionForEntry()}}|https://github.com/mongodb/mongo/blob/6edb5ef80106eb8a2d243b611208c38c635adc58/src/mongo/db/repl/oplog_applier_batcher.cpp#L263]. The function returns whether the entry should be {{kProcessIndividually}} or {{kStartNewBatch}}, which the
Fixed Versions
9.1.0-rc0
SERVER-132541ClosedWon't Fix
Consider waiting instead of immediately failing snapshot reads if no committed snapshot is available yet
Currently a node that just stepped up as writable primary can [fail \{readConcern: {level: "snapshot"}} reads with a SnapshotUnavailable: "No committed OpTime for snapshot read"|https://github.com/mongodb/mongo/blob/804b9bc48e991a9702c14eab4dd2e9e4d2001312/src/mongo/db/read_concern_mongod.cpp#L404-L406] until it can manage to advance the committed snapshot via the JournalFlusher.
This behavior is surprising considering [majority reads|https://github.com/mongodb/mongo/blob/804b9bc48e991a9702c1
Affected Versions
7.0.08.0.08.2.09.0.0-rc08.3.09.1.0-rc0
SERVER-136774ClosedFixed
Complete TODO listed in SERVER-132541
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/global_catalog/metadata_consistency_validation/metadata_consistency_util.h:63
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-132541&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 descrip
Components
Replication
Fixed Versions
9.1.0-rc09.1.0-rc1025
CSHARP-6285Blocked
Consolidate MONGODB-AWS auth test cells now that EC2 works with IMDSv2
DRIVERS-3701 made {{aws_assign_instance_profile.py}} use IMDSv2, so the EC2 auth test no longer has to be skipped on Ubuntu 24.04 and macOS. Ubuntu 24.04 can then run every credential scenario, which makes the separate Ubuntu 22.04 cell redundant, and macOS gains EC2 coverage.
h2. Acceptance Criteria
* {{skip_EC2_auth_test}} is removed from the {{ubuntu-2404}} and {{macos-14}} OS values in {{evergreen/evergreen.yml}}.
* Ubuntu 24.04 runs the MONGODB-AWS tests on both net6.0 (the framework {{run
Fixed Versions
4.0.03.next
SERVER-138030ClosedDone
Drop stale jstest removals for 6.0, 7.0 and 8.0 in release-container
h2. Summary
Drops three jstest removals from {{release-container/scripts/remove_incompatible_jstests.sh}} that are no longer needed:
* 6.0: {{transaction_too_large_for_cache.js}} (6.0.5 and later)
* 7.0: {{transaction_too_large_for_cache.js}} (all versions)
* 8.0: {{exhaust.js}} (8.0.5 and later)
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-131398ClosedFixed
Consider adding POLLRDHUP to CommonAsioSession::isConnected()
It's possible that isConnected() returns true in cases where the client has sent data and then disconnected. See [this comment|https://jira.mongodb.org/browse/SERVER-130221?focusedCommentId=8651982&focusedId=8651982&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-8651982] for more context.
Fixed Versions
9.1.0-rc0
SERVER-136935ClosedFixed
Propagate CapabilityVersion at load time
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-133898ClosedFixed
Pass direction of OIL into matchesInterval
forNumberKeysMatch and other callers of matchesInterval could calculate the direction of the OIL passed into matchesInterval once and then pass it to matchesInterval. The direction of the OIL we are comparing elements to does not change once the OIL is constructed
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137384ClosedFixed
Implement "endOfTransactionScopes" for commit oplog entry
Populate the "endOfTransactionScopes" field in the "commitTransaction" oplog entry with the actual target field definitions. The field itself is optional and not set by default. Currently no code sets it. It will later be set conditionally for the commits of cross-shard transactions if the allowEndOfTransaction parameter is set at the time of the transaction commit.
Change streams can then use this information to recreate a transaction end marker across the different commits of a sharded transac
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137615ClosedFixed
Add `allowEndOfTransaction` server parameter
Adds a new runtime-settable `allowEndOfTransaction` server parameter. The parameter is default-enabled.
The parameter is currently not read anywhere, but will be in follow-up tickets for SPM-4826.
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138284ClosedFixed
index_build_killop_secondary_before_commit.js races the killOp response against the expected server crash
The second phase of {{jstests/noPassthrough/index_builds/index_build_killop_secondary_before_commit.js}} (killOp on the secondary after the index build voted for commit, failpoint {{hangIndexBuildAfterSignalPrimaryForCommitReadiness}}) intentionally crashes the secondary with fassert 51101. However the test issues the killOp with {{assert.commandWorked(secondaryDB.killOp(opId))}} before checking for the crash. The killOp interrupt is what causes the crash, so there is an inherent race between th
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136737ClosedFixed
Record baseline metrics and implement cache-eligibility gate for join plan cache entry
When inserting an entry into the join plan cache, the plan cache will execute the first batch of the plan and measure the total num of reads by the leaf stages and total number of intermediate rows produced by the join operators as well as tracking spilling. This will be used to make a decision on (1) whether the query is worth caching (the goal is to cache "fast" queries only where optimization time is significant relative to execution time) and (2) whether to replan on cache hits
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138203ClosedDone
Enable CS analysis bot to automatically analyze all open BFs assigned to CS team
SERVER-92236ClosedFixed
Chunk migrations should use short lived cancellation sources
Recipients in a chunk migration use a singleton class that [reuses a CancellationSource for each chunk receipt|https://github.com/10gen/mongo/blob/7228125e89b/src/mongo/db/s/migration_destination_manager.h#L387-L389], using it to schedule tasks to run if the migration is interrupted, as of SERVER-65947. This includes creating CancelableOperationContexts for cloning data, waiting for write concern, and most notably copying session history, which [creates a CancelableOperationContext per oplog ent
Fixed Versions
8.2.0-rc08.0.98.1.17.0.26
SERVER-112049ClosedFixed
Consider adding a warning log if setting a server parameter ends up a noop
In multiple places we use a on_update callback set properly set server parameter, and we rely on {{Client::getcurrent()}} to do so. In many of those places, we simply perform a noop in the case the current thread does not have a client.
In the case we don't have a client, we should consider adding a warning log so that calling those function on threads without client don't go completely silent. This should help diagnosing and debugging when setting a server parameter don't behave as expected.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136748ClosedFixed
[POA] unit test unprepared txns and retryable writes
Add unit / integration testing for the following:
* Ordinary unprepared transactions
* Txns that have more than one oplog entry that are linked with {{prevOpTime}}
* Txns that have an embedded DDL entry
* Retryable writes
Fixed Versions
9.1.0-rc0
SERVER-92576ClosedFixed
Remove the docsRequested option from mongot requests
Once featureFlagBatchSizeTuning is enabled, we can consider removing featureFlagBatchSizeLimit and the docsRequested option from mongot requests, since the work under featureFlagBatchSizeTuning is a superset of the work under featureFlagBatchSizeLimit.
Fixed Versions
9.1.0-rc09.1.0-rc1024
SERVER-84773ClosedDuplicate
Remove Feature Flag for PM-3509
Feature flags should be proactively removed to address technical debt.
See the [Feature Flag Github page|https://github.com/mongodb/mongo/blob/master/src/mongo/db/repl/FCV_AND_FEATURE_FLAG_README.md#feature-flags] for additional guidance.
SERVER-137553ClosedFixed
Add negative tests for landlock in the server
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138283ClosedFixed
Disable collection validation in sharded environment
Fixed Versions
9.1.0-rc09.1.0-rc1025