Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-136663ClosedFixed
scripting_legacy_mozjs_test debug mode failures
Running this test with --spider_monkey_dbg=True first creates a bunch of compilation errors due to missing includes:
After fixing this the test then hits multiple assertion failures because it follows a pattern which is officially not supported by SpiderMonkey, shutting down and the re-initializing multiple ScriptEngines within the same process. This leads errors with the engine state and potentially memory corruption issues.
These issues are not related to the current ESR 153 up
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137708ClosedFixed
Add standby watermark metrics
Add metrics for watermarks recorded in {{recordWatermark()}} and watermarks evicted/popped in {{mergeAndValidate()}} ([code|https://github.com/10gen/mongo/blob/master/src/mongo/db/replicated_fast_count/size_count_checkpoint_validator.cpp?plain=1#L331-L335]).
The motivation here is a healthy system should record and evict approximately the same number of watermarks. If not, then we aren't seeing successful checkpoints or otherwise too far behind, and we are maintaining a lot of deltas in-memor
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137730ClosedFixed
Refactor chunk migration destination recovery path
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138241ClosedFixed
Create result materializer benchmark
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-135268ClosedDone
Update HELP Playbook for HELP-98551
The information and context for HELP-98551 was flagged for adding to the HELP Playbook. As owner of the original HELP issue (Assigned Teams), please review the linked issue and update the playbook accordingly
SERVER-137414ClosedFixed
Capture initial index build drain tail
Add helpers to capture and retain each index’s initial physical side-write tail, including invisible and prepared records. Support capturing all index tails before draining any index, preserving the boundaries across retries and recording initially empty tables.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137400ClosedFixed
Introduce explicit index build drain-phase plumbing
Pass an explicit drain phase through the index-build draining APIs, distinguishing work before readiness, after readiness, and during the final drain. This preparatory change preserves existing behavior while enabling phase-specific conflict handling.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137220ClosedFixed
Preserve recovered multikey state on callback errors
Preserve pending recovered multikey state when the index-drain callback throws, as well as when it returns an error. Ensure a subsequent drain attempt reports that state again rather than losing it after a failed batch.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137219ClosedFixed
Add ability to throw on prepare conflicts
Add a prepare-conflict mode that throws instead of blocking inside the storage operation. Include the notification generation in the error and count the conflict, allowing callers to roll back, release resources, and then wait before retrying.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137364ClosedFixed
Add prepare conflict error code
Introduce a dedicated PrepareConflict error with extra information carrying the prepare-resolution notification generation. Preserve this information through Status conversion and serialization so callers can wait for resolution without missing notifications.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137513ClosedGone away
Complete TODO listed in SERVER-134300
There is a TODO in code owned by your team which references a resolved ticket.
The TODO appears in:
* buildscripts/modules/atlas/format_snapshot_bucket.sh:145
* buildscripts/modules/atlas/format_snapshot_bucket.sh:174
* buildscripts/modules/atlas/format_snapshot_bucket.sh:308
* src/mongo/db/modules/atlas/jstests/disagg_storage/format_snapshot/libs/snapshot_helpers.js:134
You can also search for all references to the resolved ticket here:
https://github.com/10gen/mongo/search?q=SERVER-134300&ty
SERVER-137363ClosedFixed
Decouple visibility classification and WT configuration from enum layout
Replace enum-indexed WiredTiger configuration selection with explicit mappings and centralize the classification of behaviors that ignore prepare conflicts. Preserve existing behavior while allowing additional prepare-conflict modes to be introduced safely.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138420ClosedFixed
Fix windows compilation issue in sbe_streaming_agg_test
Resolves a Windows compilation failure for this unit test. {{long}} isn't a valid BSON arithmetic type. On linux this value was implicitly converted to {{long long}}, but on Windows this triggered a compilation failure.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137362ClosedFixed
Separate prepare conflict counting from waiting
Separate prepare-conflict counting from tracking blocked waits and their duration. Allow conflicts to contribute to per-operation and global metrics without marking the operation as waiting on a prepare conflict.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137218ClosedFixed
Expose prepare-resolution notification waits on RecoveryUnit
Expose a storage-engine-independent RecoveryUnit API for capturing a prepare-resolution generation and waiting interruptibly for a newer notification. This allows callers to release locks and storage transactions before waiting, without missing a concurrent commit or abort notification.
Fixed Versions
9.1.0-rc09.1.0-rc1025
NODE-7962Investigating
Support Node27
h3. Use Case
As a... _(who is this for)_
I want... _(what is the desired change)_
So that... _(why is the change desired)_
h3. User Experience
* _What is the desired/expected outcome for the user once this ticket is implemented?_
* _If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?_
h3. Dependencies
* _upstream and/or downstream requirements and timelines to bear in mind_
h3. Risks/Unknowns
* _What could go wrong while im
NODE-7933Backlog
Validate long UTF-8 strings with buffer.isUtf8 in js-bson deserializer
h3. Use Case
*As a* js-bson user
*I want* UTF-8 validation of long string values during deserialization to be faster
*So that* default deserialization (validation on) costs less for documents with long strings
h3. User Experience
No API change. For strings of 64 bytes or more, {{nodeJsByteUtils.toUTF8}} with {{fatal: true}} validates the bytes with Node's native {{isUtf8}} (from the {{buffer}} module) before decoding. Invalid input still goes through {{{}parseUtf8(..., true){}}}, so the
Components
BSON
NODE-7931Ready for Work
Migrate macOS 14 tests to macOS 15
This ticket was split from {{DRIVERS-3691}}, please see that ticket for a detailed description.
Components
Evergreen
NODE-7959Execution Blocked
Deterministic locality-aware mongos selection for multi-region sharded clusters
This ticket was split from {{DRIVERS-3604}}, please see that ticket for a detailed description.