Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139239Needs Scheduling
Avoid checksumming exhaust responses twice on the hot replication path
h1. Avoid checksumming exhaust responses twice on the hot replication path
SERVER-139492In Code Review
Split evergreen tasks for C++ integration tests
Currently, the C++ integration test tasks are organized according to the fixture they spawn or what feature flags and server paramters they use. For an example of simple fixture-based organization, integration_tests_replset is most C++ integration tests that run against a replica set. For an example of feature flagging, {{integration_tests_standalone_grpc}} runs a small set of C++ integration tests against a server with ingress gRPC enabled.
To support infinite burndown, this change splits thos
SERVER-139298ClosedFixed
Remove allowDeprecatedAfterOpTimeReadConcern from removed parameters lis
Now that SERVER-138119 is merged into master, remove this override.
Fixed Versions
9.1.0-rc09.1.0-rc1026
PYTHON-5533ClosedDone
Investigate changes in SERVER-109626: Adjust behavior for emitting additional fields in change streams
This ticket was split from {{DRIVERS-3278}}, please see that ticket for a detailed description.
Components
Change Streams
SERVER-111051Backlog
Shutdown cleanly when ESE is unable to acquire the KMIP Key
In AF-6822, we see a case where network causes us to fail acquiring the customer KMIP key. This triggers an invariant within wiredtiger, since wiredtiger_open on startup fails. Since this is not an "issue" in code, but rather a failure on startup, we should consider failing mongod more gracefully.
PYTHON-6166ClosedDone
Remove mention of waitQueueSize and waitQueueMultiple connection pool options from spec
This ticket was split from {{DRIVERS-3675}}, please see that ticket for a detailed description.
Components
CMAP
SERVER-138862Backlog
Co-change graph
Build weighted source-to-test links from Git history before the PR base. Include golden-output mappings.
SERVER-139189Open
Test initial sync and recovery components after restarting from clean / unclean shutdown
In SERVER-136961, we found a deterministic crash in FCBIS after the node restarts from an unclean shutdown. This reveals a testing gap, and we should have proper testing of each path that a node can go through after restarting from both clean and unclean shutdown.
h2. Acceptance Criteria
Targeted test that exercises every initial sync and startup recovery code path after restarting from clean or unclean shutdown. Deduplicate other tests if they already execute one of these code paths.
SERVER-130332Needs Scheduling
Switch participant term transport from $replData.term to dedicated participantTerm field once 9.0 is last-LTS
h3. Context
SERVER-128128 carries the participant replication term in {{$replData.term}} rather than a dedicated {{participantTerm}} reply field. This was necessary because adding a new top-level generic reply field and backporting it to older branches causes {{IDLUnknownField}} failures in mixed-version clusters — older mongos binaries use {{strict: true}} IDL reply structs, which reject unknown fields as hard errors.
This ticket tracks switching to a dedicated {{participantTerm}} field o
SERVER-138261In Code Review
Remove featureFlagReshardingCloneNoRefresh and featureFlagReshardingNoRefreshApplyingAndBlockingWrites refresh paths
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139311Open
Standalone mongod 8.0 loses writes acknowledged with {w:"majority", j:true} after SIGKILL (6.0 and 7.0 do not)
On a standalone {{mongod}} 8.0, a write acknowledged with {{\{w:"majority", j:true\}}} can be missing after the {{mongod}} process is killed with SIGKILL and restarted. Only the process is killed. The host keeps running, so the kernel page cache survives, and anything {{mongod}} handed to the kernel should survive too. The same probe loses nothing on 6.0.29 or 7.0.45. It also loses nothing on any of these versions when run as a three-member replica set.
h3. Repro (script below)
# Start a stand
Affected Versions
8.0.328.0.348.0.38
SERVER-139297Open
Prevent unparseable collection ID in config.image_collection
In SERVER-137912, we handle what to do if a secondary replicates an oplog entry with an invalid session ID in this collection. We should also add validation on the write/input/primary side to not allow this.
SERVER-139100Open
Add a metric to track the number of incoming connections by listener interface
Our incoming connections counters don't currently differentiate by listener interface. We should add a new otel metric which measures incoming connections with an attribute for the port that the connection was accepted on. This could be useful for internal dashboards since we could get a better idea of where incoming connections are coming from and how that would affect things like connection rate limiting among others.
SERVER-128590Needs Scheduling
$persistentStats permissions
New stage created $persitentStats that will be used to read persisted stats needs the appropriate permissions. Look into items 2 and 6 from the threat model doc in: [https://docs.google.com/document/d/1n0SPv6ur9iwzddvy__TzIJxK3pzLXr17Dh-xOB931Cg/edit?tab=t.0]
SERVER-124353Open
$persistedStats unsharded
Handle $persistedStats for unsharded collections through mongos.
SERVER-124352Needs Scheduling
$persistedStats — mongos
"$persistedStats" with allHosts support for cross-shard visibility through mongos.