Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
PYTHON-6190ClosedDone
Update lambda test Python version from 3.10
h3. *Context*
{color:#505f79}Our lambda test requires specifying a hard-coded Python version in its docker config and start script. That version is currently 3.10, which we've recently deprecated.{color}
h3. *Definition of done*
{color:#505f79}The lambda test uses 3.11 instead.{color}
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
Components
greenerbuild
NODE-7827Blocked
Misleading error message when the error returns IllegalOperation error
When the MongoDB server returns an {{IllegalOperation}} error (code 20), the NODE driver reports a misleading message:
Even for errors completely unrelated to retryWrites, end even if already using --retryWrites=false (which does not matter anyway).
h3. Expected Behavior
As a... Node Driver user
I expect... to see actual server message
When... server returns an IllegalOperation error
h3. Actual Behavior and Impact
* _What is the actual behavior?_
* _If bug: What is the number of
SERVER-137570ClosedFixed
Remove SbeCompatibility::requiresSbeFull
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-6180Ready for Work
Bundle libmongocrypt 1.21.1
Update [pymongocrypt|https://pypi.org/project/pymongocrypt/] to bundle libmongocrypt 1.21.1.
Components
pymongocrypt
PYTHON-5937ClosedWon't Do
Dependabot importlib-metadata updates (8.8+) blocked by Python 3.9 support
h2. Summary
Same root cause as PYTHON-5936. Dependabot opened [PR #2927|https://github.com/mongodb/mongo-python-driver/pull/2927] to bump {{importlib-metadata}} from {{>=7.0}} to {{>=9.0.0}}, but this cannot be adopted while PyMongo still supports Python 3.9.
h2. Root cause
* {{importlib-metadata}} *removed Python 3.9 compatibility in version 8.8.0*; v9.0.0 is the major release incorporating that (and other breaking behavioral changes, e.g. raising {{MetadataNotFound}}/{{FileNotFoundError}} ins
SERVER-137893ClosedWon't Do
Consider opting replication threads out of cache eviction
The storage engine provides an interface that allows opting specific threads out of performing optional cache eviction work, exposed via RecoveryUnit::optOutOfCacheEviction. It may make sense to opt out various replication threads (e.g. appliers) to reduce the potential for replication lag.
PYTHON-5936ClosedWon't Do
Dependabot requests updates (2.33+) blocked by Python 3.9 support
h2. Summary
Dependabot keeps opening PRs to bump the {{requests}} dependency (e.g. [PR #2931|https://github.com/mongodb/mongo-python-driver/pull/2931], which bumps {{requests>=2.23.0,<3.0}} -> {{requests>=2.34.2,<3.0}}), but these cannot be adopted while PyMongo still supports Python 3.9.
h2. Root cause
* {{requests}} *dropped support for Python 3.9 in version 2.33.0* (2026-03-25), following Python 3.9 end-of-life. See the [requests changelog|https://github.com/psf/requests/blob/main/HISTORY.md
SERVER-137185ClosedDone
GenerateAndCheckPerfResults passes failed threshold checks when the override lookup errors
Since SERVER-136977, CheckPerfResultTestCase.run_test catches every exception other than ServerFailure and TestFailure, logs it, and lets the test pass. When a metric fails its threshold check on a PR or merge queue run, _check_thresholds looks up override comments through the GitHub API: get_pull, get_issue_comments, get_review_comments, and get_comments. An error from any of these calls is swallowed by run_test, so a confirmed regression with no authorized override is reported as passing.
Bef
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-5718Ready for Work
Update attribute name in OpenTelemetry Spec
This ticket was split from {{DRIVERS-3393}}, please see that ticket for a detailed description.
Components
Logging
SERVER-137346ClosedDone
Adapt release-container evergreen.yml paths to 10gen/mongo
Update pathing for evergreen project cutover.
Components
evergreen.yml
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-1634Ready for Work
Provide a way to join background threads when closing a MongoClient
MongoClient.close() closes its sockets and signals its background threads to exit but it does not actually wait for the threads to exit (via join). This is problematic when using a MongoClient from a subinterpreter. Even when closing the MongoClient, an error gets raised when closing the subinterpreter: {{Py_EndInterpreter: not the last thread}}
Reported in: https://groups.google.com/d/msg/mongodb-user/vgsE6MpcyGE/1xm-WXMrAAAJ
and: https://groups.google.com/forum/#!topic/jep-project/lAv7-HVA
SERVER-137811ClosedFixed
Fix code/symbol cases in sbe value -> Value conversion
Previously the {{convertToValue}} cases for symbol and code would return a Value with type string, rather than with type code or symbol. This fixes those cases and adds testing for it
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-6193ClosedDone
Add ServerDescription filter to test.test_client.TestClient.test_continuous_network_errors
h3. *Context*
test.test_client.TestClient.test_continuous_network_errors is flaky, especially on gevent, due to how it counts ServerDescription instances. Filtering only the instances created by the test's client will isolate it much better.
h3. *Definition of done*
test.test_client.TestClient.test_continuous_network_errors only counts ServerDescriptions created by its own client.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
SERVER-134978ClosedFixed
Change codeowners for components that previously were owned by QI
This is to reflect the team charter change related to QI moving to Database Experience org. Based on the discussion within the team, the initial proposal is the following:
Fixed Versions
9.1.0-rc09.1.0-rc1024
SERVER-132874ClosedFixed
Add error band to fix polygon ring edges cross validation failure in Geo object parsing.
This is a follow-up from https://jira.mongodb.org/browse/SERVER-129401.
In this ticket, we will address the 2nd type of parsing validation inconsistency between different platforms (due to different glibc libs), due to sin/cos calculation rounding error.
For a polygon ring, `S2Loop.isValid()` will check if non-adjacent edges cross or not. Due to the sin/cos rounding error, the same ring may pass the check on one platform, but fail with "Edges x and y crosses" error.
The ticket is o
Fixed Versions
9.1.0-rc09.1.0-rc1024
NODE-7922Backlog
js-bson - PR #953: perf: cache short ASCII field names in the deserializer
[billouboq|https://github.com/billouboq] has created [PR #953: perf: cache short ASCII field names in the deserializer|https://github.com/mongodb/js-bson/pull/953] in [js-bson|https://github.com/mongodb/js-bson]
Components
BSONPerformance
NODE-7920Backlog
js-bson - PR #951: perf: measure each element name once in calculateObjectSize
[billouboq|https://github.com/billouboq] has created [PR #951: perf: measure each element name once in calculateObjectSize|https://github.com/mongodb/js-bson/pull/951] in [js-bson|https://github.com/mongodb/js-bson]
Components
BSONPerformance
NODE-7916Backlog
js-bson - PR #946: perf: check serialized keys for null bytes with String#includes
[billouboq|https://github.com/billouboq] has created [PR #946: perf: check serialized keys for null bytes with String#includes|https://github.com/mongodb/js-bson/pull/946] in [js-bson|https://github.com/mongodb/js-bson]
Components
BSONPerformance