Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-136879ClosedDuplicate
Show query memory load shedding stats in Atlas cluster stats view
Under IWM, some stats are already visible for IRL, etc.
SERVER-139223In Code Review
Remove BSONElementValue from src/mongo/bson/column/bsoncolumn_helpers.h
Since we want to remove BSONElementValue (see SERVER-138995) a stepping stone along that way is to remove it from this file
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-88498ClosedWon't Do
Retry analyzeShardKey command on StaleConfig error even when balancer is off for FSM test
Currently the analyze_shard_key.js FSM test only retries StaleConfig errors for the analyzeShardKey command when the balancer is on. But it is possible to get StaleConfig errors even when the balancer is not on. Instead, the analyzeShardKey command should always be retried on StaleConfig error and not be conditional on the balancer being on.
SERVER-139096ClosedFixed
Always use JOO sample size regardless of global enablement status
primary code site: [https://github.com/10gen/mongo/blob/599ccaadceb3afe90b11b3d9fd10d9bfe8b4aadf/src/mongo/db/commands/query_cmd/analyze_cmd.cpp#L274-L280]
Currently, the analyze command only uses the maximum sample size (between CBR's 384 and JOO's 1063) when JOO is globally enabled. This works for now, but the join team is planning to allow enablement of JOO for specific queries via PQS (even when JOO is not globally enabled).
Because of this, we'll need to use JOO's sample size in all c
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138771Open
Identify candidate workloads and tentative performance goals for conflict detection
h2. Overview
Select candidate workloads for measuring the success of the conflict detection architecture, measure the prototype against the existing write path, and propose tentative performance goals.
h2. Scope of Work
* Candidate workloads, e.g. TPC-C, hot-key contended transactions, YCSB, and random-key multi-document transactions (write amplification).
* Measure abort rate, commit latency, apply lag and throughput vs. the existing path. YCSB measurements can begin before detector int
SERVER-137358ClosedFixed
Enabled targeted testing suites in POA build variant
SERVER-136749 excluded targeted test suites such as {{disagg_storage}}. They have been tagged with {{incompatible_with_pipelined_oplog_applier}}. We should re-enable them.
Fixed Versions
9.1.0-rc0
SERVER-138256ClosedDuplicate
[POA] Have POA adhere to oplog applier impl failpoints
Unfortunately many tests depend on this and so we need POA to call it.
SERVER-138761Open
Prototype StagedWriteBuffer and staging hooks in the WiredTiger write helpers
h2. Overview
Prototype staging of table-level writes in a per-RecoveryUnit buffer, following the design note. Writes that would be sent to WiredTiger are recorded in the buffer instead, and every written key is added to the transaction's {{WriteSet}}.
h2. Scope of Work
* {{featureFlagStagedWrites}} (startup/FCV-gated, read once) and ident eligibility: {{kAllExceptDenyList}} (default), {{kNone}}, and test-only {{kAllowList}} driven by an internal server parameter.
* Deny-list: oplog, catalog/siz
SERVER-137930In Code Review
Migrate internal artifact producers and consumers to task-owned uploads
h2. Problem
Shared internal artifact destinations allow different tasks or variants to overwrite one another. Adopt the task-owned uploader and update consumers together after uploader infrastructure and provenance support.
h2. Scope
* Migrate binary, symbol, source, venv, BEP, benchmark, plugin, package/crypt, Streams, and supplementary build uploads.
* Select download paths from the actual producing task and variant.
* Wire release binaries, provenance, execution logs, installers, and Streams
Components
Build
SERVER-138767Open
Prototype primary oplog application with write acknowledgment and read timestamp changes
h2. Overview
Apply the primary's own oplog entries for opted-in writes using the existing OplogApplier machinery, and adjust write acknowledgment and read timestamp selection so read-your-writes behavior is preserved.
h2. Scope of Work
* Run the batch OplogApplier on the primary, tailing from lastApplied; skip entries for non-opted-in writes (already applied).
* Separate lastWritten (oplog committed) from lastApplied (applied by the primary applier).
* Write concern (including w:1) waits for th
SERVER-136608Backlog
Collect and reuse persistent stats in dbt5 joo
We should also consider creating HLL sketches. This may be valuable to ensure stability, but that would only work if we reuse the same persistent sample across runs.
SERVER-139008ClosedDuplicate
Use patched Node 22 for Bazel and jstestfuzz
Upgrade Bazel tooling and jstestfuzz to Node 22.23.4 for [CVE-2026-111497|https://nvd.nist.gov/vuln/detail/cve-2026-111497]. Upgrade rules_nodejs to 6.7.7 and share platform repositories.
Pin deterministic jstestfuzz and four legacy Evergreen tasks to merged commit {{0584b664}} from [jstestfuzz #1544|https://github.com/10gen/jstestfuzz/pull/1544], including runtime and self-test setup fixes. Regenerate {{{}MODULE.bazel.lock{}}}.
Validation: rebased onto current master; deterministic aggreg
Components
Bazel
SERVER-136458ClosedFixed
Upgrade legacy MozJS/SpiderMonkey to ESR 153 on pre-9.0 branches
Similar to SERVER-136253, but creating a separate ticket for pre-9.0 branches because the code has diverged significantly and a simple cherry-pick backport from master to 8.3 may not be possible.
Fixed Versions
8.3.18
SERVER-135427Investigating
Implement refresh logic as first write gen+1 and then delete all previous gen_ids. Without a TXN
Implement refresh logic as first write gen+1 and then delete all previous gen_ids
SERVER-138253ClosedFixed
[POA] Validate may run mid batch
Classic oplog application has the [following locks|https://github.com/mongodb/mongo/blob/d846616dd9b6551f7fb7d0e3741afbc16f368aed/src/mongo/db/repl/oplog_applier_impl.cpp#L446-L450] to prevent fsync and validate from running mid batch:
Does POA needs the same?
*This ticket is to handle VALIDATE only*. See SERVER-139205 for fsync.
Solution idea:
Each time a batch is dispatched, POA takes the validation lock in MODE_IX. The lock is stashed with the rest of the in-flight batch's metadat
Fixed Versions
9.1.0-rc0
PYTHON-5867ClosedGone away
[Test Failure] test.asynchronous.test_dns.TestDNSRepl.test_parent-part-mismatch4
h3. *Name of Failure:*
test.asynchronous.test_dns.TestDNSRepl.test_parent-part-mismatch4
h3. *Link to task:*
https://spruce.corp.mongodb.com/task/mongo_python_driver_mongodb_v4.2_test_server_version_pypy3.11_async_auth_ssl_sharded_cluster_patch_06041261cb9020e4279db749f56a476156820e02_6a26d0d9b9e75f0007a89bfa_26_06_08_14_25_57/tests?execution=0&sorts=STATUS%3AASC
h3. *Context of when and why the failure occurred:*
PyPy garbage collection issues that expose potential socket leaks.
h3.
Components
Tests
PYTHON-5916ClosedGone away
[Test Failure] test.asynchronous.test_csot.TestCsotGridfsAdvanced.test_timeoutMS_applied_to_update_during_a_rename
h3. *Name of Failure:*
test.asynchronous.test_csot.TestCsotGridfsAdvanced.test_timeoutMS_applied_to_update_during_a_rename
h3. *Link to task:*
https://spruce.corp.mongodb.com/task/mongo_python_driver_test_macos_arm64_test_standard_latest_python3.12_async_noauth_ssl_replica_set_cov_patch_ed81f02faed9ad4cb2e0fa06887c981e952f909e_6a456998b5912b000778f673_26_07_01_19_25_15/tests?execution=0&sorts=STATUS%3AASC
h3. *Context of when and why the failure occurred:*
Test has a very tight 75ms tim
PYTHON-5910ClosedGone away
[Build Failure] test.asynchronous.test_concurrency.TestAsyncConcurrency.test_concurrency
h3. *Name of Failure:*
test.asynchronous.test_concurrency.TestAsyncConcurrency.test_concurrency
h3. *Link to task:*
https://spruce.corp.mongodb.com/task/mongo_python_driver_mongodb_rapid_test_server_version_python3.10_async_auth_ssl_sharded_cluster_min_deps_cov_bb7a81f1e01d00d9534da0c114f9e7b9f9f76b7c_26_06_30_13_42_02/tests?execution=0&sorts=STATUS%3AASC
h3. *Context of when and why the failure occurred:*
Test is extremely dependent on host conditions.
h3. *Stack trace:*
{code:
PYTHON-5493ClosedGone away
[Build Failure] Connection_checkout_fails_due_to_error_establishing_connection
h3. *Name of Failure:*
test.test_connection_logging.TestConnectionLoggingConnectionLogging.test_Connection_checkout_fails_due_to_error_establishing_connection
h3. *Link to task:*
https://spruce.mongodb.com/task/mongo_python_driver_mongodb_rapid_test_server_version_python3.9_sync_auth_ssl_standalone_cov_bfaab82e2644a9d6867626cff08c1ff7d30517a3_25_07_31_15_40_02/tests?execution=0&sorts=STATUS%3AASC
h3. *Context of when and why the failure occurred:*
Test resync: https://github.com/mongodb
Components
Spec Comp