Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
NODE-7580Backlog
Make OpenSSL 4 crypto hooks work with client encryption
h3. Use Case
As a... user running {{mongodb-client-encryption}} on a system where Node.js links against [OpenSSL 4 library|https://openssl-library.org/post/2026-04-14-openssl-40-final-release/]
I want... he driver to use native OpenSSL crypto hooks
So that... I get the same performance and code path as users on OpenSSL 3 systems, rather than silently falling back to 5x slower JS-based crypto hooks.
*Note:* OpenSSL 4.0 is {color:#de350b}not{color} an LTS release but 4.2 in April 2027 will
Components
Client Side Encryption
SERVER-139042ClosedDuplicate
Use high-memory r8g hosts for RHEL 8.8 ARM64 release builds
[SERVER-139040|https://jira.mongodb.org/browse/SERVER-139040] switches RHEL 8.8 ARM64 release builds from {{m8g.4xlarge}} to {{r8g.4xlarge}}, doubling memory at the same core count to address release-build OOM failures such as [BF-47163|https://jira.mongodb.org/browse/BF-47163].
Update the release compile hosts and matching ARM64 large-host settings in {{etc/evergreen_yml_components/variants/ibm/test_release.yml}} and {{etc/evergreen_yml_components/variants/rhel/test_release.yml}}. Release work
Components
Build
SERVER-132519ClosedDone
Documentation Updates
This ticket is to update all types of documentation API Guide,
Programming Guide, and Architecture Guide related to the project.
SERVER-132717In Progress
Record getMore errors raised after a cursor has been exhausted
Cursor read errors on mongod are recorded by stamping the error code on the ClientCursor, so that the query stats entry written when it is disposed attributes the failure to the query shape.
This does not work for the last getMore of a cursor's life. When a getMore exhausts its cursor, acquireLocksAndIterateCursor() deletes the cursor as it returns, and ClientCursor::dispose() writes the shape's entry at that moment, as a success. Anything that throws afterwards (in production, only the line
SERVER-134985ClosedFixed
Enable collection of write failures for inserts on mongod
Remove the non-read guard in collectQueryStatsMongodReadErrored
Write tests to make sure thrown errors are recorded in query stats, e.g. WouldChangeOwningShard
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-133124ClosedWon't Fix
Refactor query stats read errors unit tests
Clean up query_stats_store_test.cpp after all read errors unit tests are added.
Some things to clean up:
* Add a QueryStatsErrorsTest : QueryStatsStoreTest fixture holding the flag guard as a member so unittest::ServerParameterGuard errorsEnabled("featureFlagQueryStatsErrors", true) isn't repeated
* If SERVER-131927 changes makeFindKeyFromQuery to return unique_ptr<key> instead of const key, then the lambda on 344-347 can be removed (currently builds the key twice - once to hash and once
SERVER-132529ClosedFixed
Refactor query stats read errors integration tests
Clean up query_stats_errored.js after all reads tests are added.
Some things to clean up:
* Reorganize as one outer describe per topology (standalone / replset / sharded), with non-cursor vs. cursor errors as nested describes. Right now, there are 2 standalone blocks that start 2 mongods to run the same coll.drop + insert on 3 docs
* assertOnlyErroredEntry() and assertErroredCursorEntry() share most of the same logic - could be cleaned up + moved to query_stats_utils.js
* Add an assertN
Fixed Versions
9.1.0-rc0
SERVER-136773ClosedFixed
Complete TODO listed in SERVER-132417
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/query/client_cursor/collect_query_stats_mongod.cpp:60
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-132417&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
Fixed Versions
9.1.0-rc0
SERVER-129075Backlog
Complete TODO listed in SERVER-121988
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-121988&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.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-139124Backlog
Optimize bazel_rules_mongo's get_diff_revision
1. Check the cheap case first - for example, we would never have to initialize a Repo() if we fall into this else branch
2. Regarding the if expansions.get("github_pr_number", None): branch above, we could write it like this to avoid enumerating branches
We use get_diff_revision in a few places to to revolve a diff of what the current
"changes under test" are.
SERVER-136833Backlog
Think about ASC testing and longer-term ASC compatibility with SPM-4740
SERVER-139066ClosedGone away
Complete TODO listed in SERVER-138112
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* src/mongo/db/index_builds/index_builds_coordinator.cpp:3717
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-138112&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 represen
PYTHON-6240ClosedDone
Enable ruff LOG rules
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
Ruff 0.16.0 added the {{LOG}} category of rules derived from the flake8-logging linter.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Remove the suppression of {{LOG}} rules or add an explicit comment explaining why keeping it suppressed is correct.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
PYTHON-6254ClosedDone
Use Ubuntu 24 for i686 wheel build jobs
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
The i686 wheel build GHA job [has been failing|https://github.com/mongodb/mongo-python-driver/actions/runs/42856444629/job/129996440826?pr=3191] since {{ubuntu-latest}} switched to Ubuntu 26.
This is because i686 uses the legacy {{socketcall}} syscall rather than the newer {{socket}}. The current image that {{ubuntu-latest}} points to rejects the legacy call and causes DNS lookup to fail before it can reach PyP
SERVER-138588Open
Revisit resumable_primary_driven_index_builds_incompatible tag
There are two jstests with this tag.
{{jstests/noPassthrough/index_builds/abort_primary_driven_index_build_if_interrupted_by_failover.js}} was from pre-resumable-pdib era that assumes index builds are alway aborted. We could update it to only run when
featureFlagResumablePrimaryDrivenIndexBuilds is disabled.
{{jstests/core/query/id_field_special_cases2.js}} was because "Test uses findAndModify" but it should've been fixed now.
SERVER-138587Open
Revisit resumable index build tests disabled for PDIB
We excluded tests that required resumable index builds from PDIB when PDIB wasn't resumable. We should revisit and try to reenable them now.
There's the requires_index_build_resumability [tag|https://github.com/mongodb/mongo/blob/master/buildscripts/resmokeconfig/matrix_suites/overrides/primary_driven_index_builds.yml#L53-L54], but a number of tests are tagged with the generic primary_driven_index_builds_incompatible and the reason given was "Primary-driven index builds aren't resumable". We sh
SERVER-138193ClosedDeclined
Refactor Index Traversal in collection validation to prepare for parallel traversals
Index traversal cannot be run in parallel on multiple indexes as it modifies shared state.
Refactor index traversal to avoid shared state modification so dispatch can be parallel.