Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-137892ClosedDone
Investigate noPassthrough sharding coverage for tests compatible with replSetStepUp optimization
The missing [{{replSetStepUp}}|https://github.com/10gen/mongo/blob/a84b197701e3cdd4b52e43c82512a38c85b9592a/src/mongo/db/repl/repl_set_commands.cpp#L818-L852] optmization was implemented through SLS-1695. More precisely, SERVER-121958 restored the optimization allowing the fixture to proactively request promotion instead of waiting for automatic primary selection.
As part of this ticket, we will investigate the {{replSetStepUp}} current coverage concerning proactive promotion during restarts
NODE-7642Backlog
respect Binary position in toExtendedJSON
h3. Expected Behavior
As a user of js-bson
I expect only written bytes of a Binary to be encoded
When calling toExtendedJSON
h3. Actual Behavior and Impact
* calling toExtendedJSON will base64 document values representing the full underlying buffer for binary types, not just the data therein.
* No known customer reports today.
h3. Dependencies
* _None_
h3. Risks/Unknowns
* Any consumer that was inadvertently relying on the padded base64 output (e.g., reading the full 256-by
Components
BSONEJSON
SERVER-125618ClosedFixed
Create a suite with lagging secondaries for sharded clusters
There currently exists a [background hook|https://github.com/mongodb/mongo/blob/cd90f28f0a69ab94a913fb5310a69a7602e2f107/buildscripts/resmokelib/testing/hooks/secondary_lag.py] where it forces secondaries to be lagging.
However, this hook is currently only used in suites for replica sets. We should expand the testing to also have a sharded cluster version that uses this in conjunction with any other relevant background hooks in order to ensure lagging secondaries do not cause a problem.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138628ClosedFixed
CurOp index build collection scan message inconsistent with listIndexes build info
Restore the SERVER-89672 fix reverted in SERVER-106407 by accident.
Fixed Versions
9.1.0-rc09.1.0-rc1025
PYTHON-6224ClosedFixed
[BF] Startup failure on Amazon Linux arm64
h3. *Name of Failure:*
Evergreen task {{test-no-toolchain-sync-auth-ssl-sharded-cluster}} on {{other-hosts-amazon2023-latest}} fails in {{run server}} before any test executes (0 failed tests). Siblings {{test-no-toolchain-async-noauth-ssl-replica-set}} and {{test-no-toolchain-sync-noauth-nossl-standalone}} fail identically.
h3. *Link to task:*
https://spruce.corp.mongodb.com/task/mongo_python_driver_other_hosts_amazon2023_latest_test_no_toolchain_sync_auth_ssl_sharded_cluster_patch_063
Components
InfrastructureTests
Fixed Versions
4.20.0
SERVER-138300ClosedDone
Add server_task_id patch parameter to release-container
h2. Summary
* Adds a {{server_task_id}} parameter to {{release-container/evergreen.yml}}.
* When set, {{build-container}} passes {{--task-id}} to {{build_image}} so enterprise images are built from the "Dist Tarball" of that server {{package}} task instead of the published tarball. {{build_image --task-id}} already existed.
* Defaults to empty, so cron and normal runs are unchanged. Skipped for community installs, which {{build_image}} rejects.
h2. Usage
{{evergreen patch -p <release-container-
Components
Build
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-137669ClosedFixed
Create router synthesis stage skeleton
Create a skeleton implementation for the router synthesis stage, as defined in the [technical design here|https://docs.google.com/document/d/1GOKV_XtQeUXd9PMBgRtfXN8X-dLEomIUhqUZ_AbfsVs/edit?tab=t.mpeiqjdoks5b#bookmark=id.4bkjwvg30u2h].
The stage should let all non-control events through unmodified. It should fail when receiving topology control events, because these are never expected to reach the stage.
For change stream accounting control events, it should perform the per-transaction en
Components
Change streams
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138217ClosedDone
Update certifi in mongo server container
Make sure we have the latest certifi to remediate the emudhra certificate vulnerability.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138563ClosedDone
Exclude fuzz targets from the Windows compilation database
Fixes BF-47088 ({{full_bazel_compiledb}} on {{enterprise-windows}}).
SERVER-136567 added {{mongo_cc_fuzztest}}, deprecated fuzzers and {{bson_mutator}} to {{compile_commands.json}} under {{--config=compiledb}} on every platform. On Windows, {{validate_compile_commands}} replays those entries with MSVC, but FuzzTest/Centipede need a POSIX/Clang toolchain ({{endian.h}}, {{pthread.h}}, {{__builtin_*}}, {{__PRETTY_FUNCTION__}}). That is 53 failed compilations since 10/20 (first bad commit {{506fa21
Components
Bazel
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138318ClosedDone
Restore transaction_too_large_for_cache removals for 6.0 and 7.0 in release-container
Restores the removal of {{jstests/core/transaction_too_large_for_cache.js}} in {{release-container/scripts/remove_incompatible_jstests.sh}}:
* 7.0: all versions
* 6.0: 6.0.5 and later
The 8.0 {{exhaust.js}} removal dropped in the same commit is intentionally not restored.
*Why:* a9b768b208a (SERVER-138030) dropped these removals as stale TODOs, but the test still fails in the container. The default WiredTiger cache there is large enough that the 16MB, 62-index insert succeeds instead of return
Components
Bazel
Fixed Versions
9.1.0-rc09.1.0-rc1025
GODRIVER-4239Needs Triage
[spike] Decide handling of | in DriverInfo on paths that can't return an error
h3. *Context*
On the paths that can't return an error, SetDriverInfo + newClient, a DriverInfo containing {{|}} is silently dropped, so the wrapper is missing from telemetry. The spec requires an error, but returning one from Connect would be a breaking change. Options are dropping it (current), replacing the {{|}}, logging a warning, or treating this as a bug and making a breaking change.
h3. *Definition of done*
TBD
Caution against making a breaking change, this worked as designed b
SERVER-136270ClosedFixed
Add def/use mappings to SBE blueprint
Remove $search from SBE
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-134410ClosedFixed
Fix quadratic document-stream generation in the timeseries write-path PBT arbitraries, and restore kCount coverage
Fixed Versions
9.1.0-rc09.1.0-rc1024
SERVER-137905In Code Review
add a pre-scan check for prepareConstraintLevel to collMod
The prepare precondition is only checked after the validator scan in collmod_cmd.cpp / collmod_coordinator.cpp has already run. A request with prepare unset therefore does a full collection scan before being rejected with BadValue. We should do a cheap precondition check before the scan.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-97335ClosedFixed
Fix crash in shell_utils when using simple collator
[BF-35734|https://jira.mongodb.org/browse/BF-35734] surfaced an issue in the mongo (shell) executable.
The shell's `_compareStringsWithCollation` function creates a collator object from BSON and then calls a method on it.
However, `CollatorFactoryICU` [can also return a nullptr|https://github.com/10gen/mongo/blob/2e1e319f2975a4b5194e75f42a6af7197b5419bc/src/mongo/db/query/collation/collator_factory_icu.cpp#L527] when the BSON object contains
In this case the caller must check the retu
Components
Shell
Affected Versions
8.1.0-rc0
Fixed Versions
8.1.0-rc0
SERVER-121289ClosedFixed
Make timeseries create path idempotent and concurrency safe
The current timeseries creation path is affected by several issues:
- view and non-timeseries creation does not check for the presence of legacy system.buckets collection leading to the creation of both main namespace and legacy system.buckets collection (no concurrency required)
- view and non-timeseries creation are not serialized properly with legacy timeseries creation leading to the creation of both main namespace and legacy system.buckets collection (concurrency required)
- viewless an
Fixed Versions
9.0.0-rc0
SERVER-138216ClosedFixed
Have SBE blueprint rewrites report depth information
This may be useful in the future for rewrites that match on and modify grandchildren
Fixed Versions
9.1.0-rc0
GODRIVER-4187Needs VerificationFixed
getMore and killCursor fail to reauthenticate on ReauthenticationRequired (391)
h3. Detailed steps to reproduce the problem?
getMore and killCursor do not reauthenticated on [ReauthenticationRequired (391)|https://github.com/mongodb/mongo/blob/master/src/mongo/base/error_codes.yml#L862C23-L862C47]
Repro: https://github.com/10gen/go-driver-tools/blob/main/preston/repros/2.9.2/godriver_4187_test.go
Public repro: https://gist.github.com/prestonvasquez/a7020ec7c7271f96e7195ab13517b8bc
h3. Definition of done: what must be done to consider the task complete?
The [aut
Components
Authentication
Affected Versions
1.17.62.9.2
Fixed Versions
2.9.3
SERVER-135874ClosedFixed
Split doesNotSupportGracefulStepdown test flag
This will complement the existing {{doesNotSupportGracefulStepdown}} flag.
Fixed Versions
9.1.0-rc09.1.0-rc1024