Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139444ClosedFixed
Give concrete FCV steps independent Bazel targets
h2. Objective
Modularize the build of the concrete steps used by the setFeatureCompatibilityVersion command. Give each concrete FCV step its own Bazel library, keep the registry/framework library independent of concrete implementations, and link the implementations into mongod through one aggregation target. Demonstrate that a concrete step can be linked and tested independently of all other steps and of the setFCV command implementation.
h2. Problem and motivation
Currently, the framew
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139525Backlog
Register bulkWrite query stats on the legacy mongos write path
SERVER-137436 registers bulkWrite ops for query stats on mongos only on the unified write executor path. When {{featureFlagUnifiedWriteExecutor}} is off, mongos runs bulkWrite through the legacy {{cluster::bulkWrite}} path, which registers nothing, so no bulkWrite query stats are recorded on mongos.
*Scope*
* Register bulkWrite ops for query stats on the legacy mongos bulkWrite path, matching the unified write executor path.
*Close-out condition*
If the unified write executor is fully rolled o
SERVER-139524Backlog
Report the bulkWrite op queryShapeHash in bulkWrite explain output
Explaining a bulkWrite with a single update or delete op reports the {{queryShapeHash}} of the equivalent standalone update/delete command, not the bulkWrite op shape hash recorded in {{$queryStats}}. The two hashes differ by design, so the hash from explain cannot be used to find the bulkWrite entry in {{$queryStats}}.
* mongos: {{cluster_bulk_write_cmd.h}} converts the op into a standalone update/delete request and runs the standalone explain path, which computes the update/delete shape hash.
SERVER-137436Investigating
Shapify bulkWrite ops on mongos
Register query shapes and stats keys for bulkWrite ops on mongos, so that mongos records a query stats entry per bulkWrite op the same way it already does for update and delete commands.
*Scope*
* In {{WriteCmdQueryStatsRegistrar::parseAndRegisterRequest}} ({{src/mongo/s/write_ops/write_cmd_query_stats_registrar.cpp}}), add a bulkWrite branch. Today it returns early for anything that is not an insert/update/delete command.
* For each op, build the bulkWrite op shape (update/delete/insert) and t
SERVER-137438Backlog
Attach metrics to bulkWrite responses on shards
On shards, when a bulkWrite op carries {{includeQueryStatsMetricsForOpIndex}}, attach that op's query stats metrics (keys/docs examined, etc.) to the bulkWrite reply, as update/delete/insert commands already do.
Depends on the bulkWrite IDL fields from SERVER-137437. mongos aggregation of these metrics is SERVER-137437.
SERVER-137437Backlog
Collect query stats for bulkWrite ops in sharded
Collect shard-side query stats metrics for bulkWrite ops on mongos, building on the per-op registration from SERVER-137436.
*Scope*
* Add an {{includeQueryStatsMetricsForOpIndex}} field to bulkWrite update/delete/insert ops, and a per-op {{queryStatsMetrics}} field to the bulkWrite reply, mirroring the update/delete/insert command IDL in {{write_ops.idl}}.
* On mongos, set {{includeQueryStatsMetricsForOpIndex}} on shard-bound bulkWrite ops that were registered for query stats, and aggregate the
SERVER-139521Backlog
Multiversion and Upgrade/Downgrade Testing
This ticket is to ensure there is adequate multiversion testing
coverage for this project.
1. Test that this feature works correctly on mixed binary version
clusters.
2. Test how the feature behaves when upgrading FCV turns the
feature on
3. Test that the correct behavior occurs when downgrading FCV
completely and then upgrading FCV completely
4. Test that the correct behavior occurs if the FCV upgrade fails.
5. Test that the correct feature behavior occurs if the FCV downgrade
fails after only
SERVER-139520Backlog
Documentation Updates
This ticket is to update all types of documentation API Guide,
Programming Guide, and Architecture Guide related to the project.
SERVER-139430In Code Review
Allow cutback at ORP staged read bounds
Add a callback between successful ORP read stages so the standby can decide whether to continue reading from ORP or return for LS cutback. Return the last successfully enqueued LSN and ensure we can tell apart cutback from a fully read stream.
SERVER-101716ClosedFixed
read_through_cache.h function throws exception on noexcept method
_doLookupWhileNotValid [throws|https://github.com/mongodb/mongo/blob/0a68308f0d39a928ed551f285ba72ca560c38576/src/mongo/util/read_through_cache.h#L593-L598] (tassert) but [is noexcept|https://github.com/mongodb/mongo/blob/0a68308f0d39a928ed551f285ba72ca560c38576/src/mongo/util/read_through_cache.h#L556].
Affected Versions
7.0.08.1.0-rc08.0.0
Fixed Versions
8.2.0-rc08.0.107.0.22
SERVER-119413ClosedFixed
configTerm is expected as an int32 but can be an int64
In repl_set_config.idl the [configTerm|https://github.com/10gen/mongo/blob/master/src/mongo/db/repl/repl_set_config.idl#L174] field has a max value of int max but is derived from the term field of the original primary. If the term that is used here were to ever be above int::max and below int64::max that would cause a parsing crash. configTerm should be parsed as a long long like other uses of term in the code.
This also requires changes to repl_set_heartbeat_response.h/cpp since we store the
Fixed Versions
8.3.0-rc08.2.78.0.217.0.32
SERVER-134166Investigating
Complete TODO listed in SERVER-121823
There is a TODO in the codebase referencing a resolved ticket which is assigned to you.
Please follow this link to see the lines of code referencing this resolved ticket:
https://github.com/10gen/mongo/search?q=SERVER-121823&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 represent the work you're actually doing.
SERVER-130386Open
Try disagg measure startup tasks with retry on crash
We run into a variety of issues when we try startup with larger number of tables (>200k). We should see what happens if we simply try to restart from where we left off if we had crashed. This allows us to uncover potentially more issues and get signal on what happens in these cases
SERVER-138011ClosedFixed
Don't rely on counting log messages in the initial sync fuzzer
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136061Open
Add connect failure backoff to page reads to avoid hot spinning and using 100% CPU
This was surfaced from HELP-100704 where SLS resolved page server addresses that didn't resolve ("Domain name not found"). This was an SLS bug but while it was broken, mongod burned 100% CPU on every read
The sendPageRequestSync loop is while(true) bounded only by the read's totalDeadline and has no sleep in order to keep page reads fast. The exponential backoff that exists is per page server in the writer thread but it fails fast. While a server is in backoff requests are rejected immediatel
SERVER-137274In Progress
Replace dummy indexes with schema constraints in JS tests
In the JS tests for JOO, we often create dummy indexes for arrayness information. Once the type inference project is ready to infer arrayness from schema constraints, these indexes should be replaced with schema constraints.